What to do while Claude Code is working
Decide by how long the run will take. For under a minute, stay with the task: reread your prompt, look at what has changed, draft the next step. For a few minutes, get up: stretch, refill your water, look at something far away. For a long run, take a proper break or do something that needs none of the same context. The habit that costs the most is the default one: opening a feed and coming back long after the agent needed you.
- The short answer
- Why the wait is hard
- Under a minute
- A few minutes
- Long runs
- What to avoid
- When it needs you
- Usage limits
- A rhythm that works
- Questions
The short answer
| How long it runs | What helps |
|---|---|
| Under a minute | Stay with the problem. Reread the prompt, scan the diff so far, write the next instruction or the test cases you’ll ask for. |
| One to five minutes | Move. Stand up, stretch, drink water, look 20 feet away for 20 seconds, do a few push-ups. Leave a one-line note of where you were. |
| Five to thirty minutes | Take a real break away from the screen, or do something that needs none of the same context: an errand, lunch, a walk. |
| A usage limit | Treat it as the break you didn’t plan. Claude Code carries on by itself after the reset. |
Why the wait is hard
Coding with an agent swaps long stretches of typing for short, unpredictable waits: twenty seconds of thinking, three minutes of edits, a test run that takes ten. Each wait is too short to start something else properly and too long to just sit through. When developers compare notes, the same two answers keep coming up. One group fills the gap with feeds and short videos and loses the thread. The other uses it to move.
The biggest thread we found, “How do you guys stay in a flow state while waiting for Claude?” on r/ClaudeCode, drew almost 250 comments. People who run many sessions in parallel admit that when none of them needs attention, they drift to their phone anyway. Others report that even two windows make them lose track, and some went back to one session at a time. Among the most upvoted practical answers, one developer does “dead hangs and push ups between Claude prompts”.
Under a minute: stay with the task
A short wait isn’t a break, and switching away costs more than it gives back. Keep the problem in your head instead:
- Reread what you asked. You’ll review the answer more critically if you remember exactly what you wanted.
- Look at what has changed so far. Claude Code shows edits as it makes them, and catching a wrong turn early saves a whole run.
- Write the next instruction or the edge cases you’ll want tests for. If the answer goes another way, you throw the draft out.
- Keep a paper note of the one thing you’re checking. It holds the context better than another tab.
A few minutes: move
This is where short breaks earn their keep. A 2022 meta-analysis of 22 studies on micro-breaks of ten minutes or less found that they made people feel more energetic and less tired, though on its own a break didn’t measurably improve performance on demanding tasks (Albulescu et al., PLOS ONE). So use the minutes for your body, not as a productivity trick:
- Stand up and stretch, or walk to the kitchen and back. Sitting still for hours is the default of agent work.
- Rest your eyes. The American Academy of Ophthalmology suggests looking about 20 feet away for 20 seconds every 20 minutes, which also reminds you to blink (AAO).
- Drink water or make tea. Small physical chores keep your hands busy and your head on the problem.
- A few push-ups or squats. Several of the developers in those threads do exactly this, between prompts.
Long runs: take a real break
When a run will take ten or twenty minutes, that’s a break, not a wait. Step away from the screen. If you’d rather work, pick something that needs none of the context the agent is using, so you aren’t holding two versions of the same problem in your head. Picking up a second coding task in the meantime is what many people describe as the most tiring option of all.
On a Claude subscription, a break doesn’t make your next prompt more expensive: within your plan’s included usage, Claude Code keeps the conversation’s prompt cache warm for an hour. With an API key, or once you’re on extra usage, the cache lasts five minutes, so the first prompt after a longer break reprocesses the conversation (prompt caching).
What to avoid
- Feeds and short videos. They aren’t harmful in themselves, but they’re built to hold you longer than a run lasts. You come back late and with the problem gone from your head.
- Checking every few seconds. Watching the spinner keeps you from both resting and thinking.
- More sessions than you can hold. Parallel sessions help when each task needs you rarely. People who run nine to twelve projects at once describe their brain as fried by the end of the day.
Don’t miss when it needs you
Stepping away only works if you hear about the moments that need you: a permission prompt or a question blocks the session until you answer. Set up an alert for those and let finished responses wait. Our guide on getting notified when Claude Code finishes or needs you shows how, for each terminal and for Claude Desktop.
When you hit a usage limit
When a claude.ai usage limit stops a session mid-task, Claude Code waits in the open session and continues on its own after the limit resets. That’s on by default, and autoContinueAtUsageLimit turns it off (usage limits). So there’s nothing to babysit. In a thread about the wait, several people say the limit is what finally makes them take a break: a workout, sunlight, something to eat.
A rhythm that works
The waits are easier when they’re part of a plan instead of interruptions. A simple one is the pomodoro: a 25-minute focus, then a 5-minute break. Give the agents their work at the start of a focus, answer what needs you as it comes, review the finished work near the end, and spend the break away from them entirely. Which rhythm suits which work is in pomodoro with AI coding agents.
That’s the rhythm Meowdoro is built around, so take this as a disclosure: we make it. It’s a focus timer that lives around the MacBook notch. During a focus it shows which Claude Code and Codex sessions are working, done or waiting for you, without a sound. During a break it hides them, and when the next focus starts, one line tells you what happened while you rested. It never answers an agent for you. It’s free before December 2026, then a one-time $20, on macOS 14 or later (how focus and breaks work).
Questions
Should I run several Claude Code sessions to fill the wait?
It works when the tasks are independent and each needs you rarely. Give each session its own git worktree so they don’t edit the same files (running agents in parallel). If you notice you’re rereading every diff twice, go back to fewer.
Can I close my laptop while Claude Code is running?
Closing the lid puts the Mac to sleep, and a session running on it stops making progress until it wakes. For a task that has to keep going, start a cloud session instead, for example with claude --cloud (Claude Code in the cloud).
What should I do while Claude is thinking for twenty seconds?
Stay. Reread your prompt or look at what has changed so far. Twenty seconds is too short to switch away and come back with your context intact.
Is it bad to scroll my phone while I wait?
Not by itself. The trouble is that a feed rarely ends when the run does. If you want to look at your phone, wait for the actual break.
Sources: Albulescu et al., “Give me a break!”, PLOS ONE, 2022; American Academy of Ophthalmology; the Claude Code documentation on prompt caching, usage limits and cloud sessions, read on October 26, 2026; discussions on r/ClaudeCode and r/ClaudeAI linked above. This isn’t medical advice: if something hurts, ask a doctor.