Guides

ADHD and AI coding agents: what helps, and how to stay out of the hyperfocus trap

Developers with ADHD often say coding agents like Claude Code and Codex help with the hardest parts of the work: starting a task, holding the context in your head, and getting through the boring steps. The same agents make it easy to lose a whole day. Every step ends in a short wait, every reply is a small reward, and there’s always one more prompt. What helps: let the agent hold the context for you, give it whole tasks instead of watching each step, time-box your sessions with real breaks, keep alerts quiet, and decide in advance when you stop. This is a guide to working with the tools, not medical advice.

What agents help with

Read what developers with ADHD write about working with agents, and the same four things come up:

The hyperfocus trap

The same features cut the other way. An agent works in steps, and each step ends with a wait: half a minute, two minutes, five. That’s too short to do anything else properly and long enough to open another tab. Jeff Putz, who writes about coding with AI and ADHD, names these waits as the main downside: they keep pulling his attention away. Then the reply comes, it’s a small win, and the next prompt is one sentence away.

None of this is unique to ADHD; anyone can get stuck in this loop. What ADHD adds is a stronger pull into it and a harder time getting out, which is why the setup below is mostly about getting out.

What the research says

Not much yet: one small study, a few surveys, and many personal accounts.

A setup that keeps the help

  1. Start with a plan, not code. Ask the agent to read the code and write a plan before it changes anything. The plan is your way into the task, and reading it is a natural point to stop and think. In Claude Code, that’s plan mode; my full prompt is in 3 Claude Code prompts I actually send.
  2. Let the agent hold the context. Keep project rules in CLAUDE.md or AGENTS.md, and before you stop, ask the agent to write down where you left off (the prompt is below). Name sessions with /rename and come back with claude --resume.
  3. Give it the whole task, then step away. Fewer check-ins beat more willpower. Hand over a task that takes it ten minutes or more, not one step at a time, and do something else until it needs you. What to do with each kind of wait is in What to do while Claude Code is working.
  4. One session at a time, two at most. Every extra session is one more thing pulling at you. More on how many sessions is too many.
  5. Time-box with a timer you can see. A pomodoro round, or a longer focus block, with a break you actually take. The timer decides when you stop, so you don’t have to notice it yourself. Which rhythm fits agent work is in Pomodoro with AI coding agents.
  6. Make alerts come to you. Turn on notifications for when the agent finishes or needs you, and stop checking. Keep them quiet during a break. How to set them up is in Claude Code notifications.
  7. Decide when you stop before you start. Pick the time. When it comes, write the notes, and if there’s work left that doesn’t need you, hand it to an overnight run with clear rules (the prompt). Stopping is easier when it doesn’t mean losing the thread.

The prompt that remembers for you

Send this before you stop for the day, or before a break you’re not sure you’ll come back from on time:

Before we stop, write NOTES.md:

- What we did today, in three lines.
- What's half-done, and in which files.
- The next step, small enough to start in two minutes.
- Anything I need to decide.

Keep it short. I'll read it first thing next time.

The line that matters most is the third. Next time, you don’t restart the task: you start a two-minute step, and the rest follows. Open the file before anything else, or tell the agent to read it at the start of the next session.

Where Meowdoro fits

We built Meowdoro, a focus timer around the MacBook notch for people who work with Claude Code and Codex, for exactly this loop. The timer sits where you can see it, the notch shows which agent is working and which one needs you, so you can stop checking, and during a break nothing reaches you while the agents wait. It isn’t a treatment for anything; it’s a timer that knows about your agents. Try it and tell us what’s missing.

Questions

Are AI coding agents good for people with ADHD?

Many developers with ADHD say they help with starting tasks, holding context and getting through boring steps. Many also describe losing hours to the prompt-and-wait loop. The research so far is small, so treat both as experiences, not proof.

Do AI agents make hyperfocus worse?

They can. Short waits and quick replies make it easy to keep going long past the point where you’re working well. A timer with a hard stop, fewer sessions and quieter alerts help.

How do I stop checking Claude Code every minute?

Give it bigger tasks, turn on notifications for when it finishes or needs you, and do something else in between. Fewer check-ins work better than trying harder not to look.

Can Claude Code remember where I left off?

Within a session, yes, and claude --resume brings a session back. Across days, it’s more reliable to ask it to write a short notes file before you stop and read it first next time.

Sources: Pimenova et al., “Two’s a Crowd: Human and AI-Based Copresence for Developers with ADHD”, arXiv, 2026; CDC, ADHD diagnosis, treatment, and telehealth use in adults, MMWR, October 2024; Stack Overflow Developer Survey 2022; Ashinoff and Abu-Akel, “Hyperfocus: the forgotten frontier of attention”, Psychological Research, 2021; Hupfeld, Abagis and Shah, “Living ‘in the zone’: hyperfocus in adult ADHD”, 2019; CHADD, on body doubling; Zachary Proser, “What It Feels Like To Be a Neurodivergent Engineer”, 2026; Jeff Putz, “Coding with AI and ADHD”, 2025. All read on November 15, 2026. This guide is about working with coding tools. It isn’t medical advice; if ADHD is getting in the way of your work, talk to a clinician.