Guides

Pomodoro with AI coding agents: 25/5, 50/10 or flowtime?

With an agent doing part of the work, a pomodoro round changes shape: you hand work over at the start, answer what needs you in the middle, review near the end and spend the break away from the agents. 25/5 fits work with short agent runs and frequent review. 50/10 fits long runs and deep review. A count-up timer, or flowtime, fits days when you’re deep in something and an alarm would cut it off. Whichever you pick, let a round run over by a few minutes rather than stopping mid-thought.

By Dmitry Mishunin, who builds Meowdoro · October 27, 2026

• The short answer
• What agents change
• One round, step by step
• 25/5, 50/10, 52/17
• Flowtime and overtime
• Several agents
• Breaks without agents
• Questions

The short answer

What agents change about a pomodoro

The classic technique, which Francesco Cirillo started with a kitchen timer in the late 1980s, assumes you do all the work: 25 minutes of focus, a short break, a longer one after four rounds. With Claude Code or Codex, part of every round is waiting. That changes three things.

• The start of a round is for handing work over. Write the prompts, set the agents going, then turn to the part only you can do: reading, deciding, testing.
• The middle is interrupted by the agent, not by you. A permission prompt or a question blocks a session until you answer, so you need to hear about those. Finished work can wait for the end of the round (how to get those alerts).
• The break competes with the agent. It’s tempting to check one more session. A break spent reading diffs isn’t a break.

One round, step by step

• Minutes 0–3: pick the task, write the prompt, start the run. If you run several sessions, give each its task now.
• Minutes 3–20: work on what the agent can’t: read the code it touches, think through the edge cases, answer its questions as they come. Ignore finished runs until the end.
• Minutes 20–25: review what finished, give the next instructions, note where you are in one line.
• The break: stand up and step away from the screen. If a run is still going, let it go. The waits inside a round are covered in what to do while Claude Code is working.

If a session’s context is filling up, the break is a good moment to compact it: run /compact before you leave and the agent does it while you rest (when to compact and when to clear).

25/5, 50/10 or 52/17?

25/5 is the classic. Its strength is that a break comes before you’re tired. Its weakness is the one developers mention most: 25 minutes can end right when a review or a thought is half done.

50/10 doubles the focus and the break. It suits work where an agent run alone takes ten minutes, so a 25-minute round would hold barely one review.

52/17 comes from a 2014 analysis by the time-tracking company DeskTime: its most productive users tended to work about 52 minutes, then step away for 17. It describes what those people did rather than a tested schedule, and a 2021 rerun of the same analysis found 112 and 26 minutes instead (DeskTime). Treat it as one more data point that longer blocks need longer breaks.

Research on short breaks points the same way. A 2022 meta-analysis found that breaks of ten minutes or less made people feel more energetic and less tired, and that more demanding work needed longer breaks to show an effect on performance (Albulescu et al., PLOS ONE).

Flowtime and overtime: when the alarm gets in the way

The most common complaint about pomodoro timers isn’t a missing feature: it’s the alarm. Two of the most upvoted pomodoro threads on r/ADHD (one, two) are about a timer that rings just as momentum builds. The fixes people suggest are softer, not stricter:

• Overtime. When the round ends, the timer keeps counting up instead of stopping you. You finish the thought and start the break yourself, a few minutes later.
• Flowtime. No fixed length at all. Start a count-up timer, work until your focus actually drops, then take a break proportional to the stretch, for example about a fifth of it.
• One quiet cue. A single soft sound, or none, instead of an alarm that repeats.

For someone prone to hyperfocus, a skippable, gentle break works better than a rigid one. The goal is to notice the time, not to be thrown out of the work.

Several agents in one round

Many people run three or more sessions in parallel. A pomodoro still works if each session gets its task at the start of the round and you check finished ones at the end. What breaks it is answering every finished session the moment it finishes: you spend the round switching. If you catch yourself rereading every diff twice, run fewer sessions per round.

Keep breaks free of agents

A break only helps if it’s a break. Close the terminal view, put the phone face down and do something physical. On a Claude subscription, Claude Code keeps a conversation’s prompt cache warm for an hour, so a 5- or 15-minute break doesn’t make your next prompt more expensive (prompt caching).

We built Meowdoro around exactly this, so here’s the disclosure: we make it. It’s a focus timer in the MacBook’s notch. During a focus it shows which Claude Code and Codex sessions are working, done or waiting for you, silently. During a break it shows only the cat and the time, even if agents are waiting, and when the next focus starts, one line says what happened while you rested. It counts overtime, can start the next phase on its own, and names a session that’s worth compacting on the break card. It’s free before December 2026, then a one-time $20, on macOS 14 or later (the timer · focus and breaks).

Questions

Which is better, 25/5 or 50/10?

Neither in general. 25/5 suits short agent runs and frequent review, 50/10 suits long runs and deep review. Try each for a few days and keep the one after which you feel less drained, not the one with the most rounds.

What is the 52/17 rule?

Work about 52 minutes, then take about 17 off. It comes from a 2014 DeskTime analysis of its most productive users, which observed what they did rather than testing a schedule. A 2021 rerun found 112 and 26 minutes.

Does the pomodoro technique work for programmers?

It works for many, mostly as a reminder to take breaks and to start. The common objection is that a fixed alarm breaks flow; overtime or flowtime fixes most of that.

What should I do with an agent that’s still running when the break starts?

Let it run. If it needs you, it will wait. You’ll answer faster after a real break than during a half one.

Sources: Albulescu et al., “Give me a break!”, PLOS ONE, 2022; DeskTime on the 52/17 ratio; the Claude Code documentation on prompt caching, read on October 26, 2026; the r/ADHD threads linked above.