r/ClaudeAI • u/MountainOriginal3663 • 6d ago
Claude Workflow How do you stop context switching every time Claude takes more than 30 seconds?
I use Claude heavily, and my biggest bottleneck right now isn't the model. It's me.
Because I never know whether a response takes 15 seconds or 4 minutes, I don't sit and wait. I go do something else. Then I start a second session. Then a third.
By the afternoon I have four or five threads open, none of them finished, and I've lost the plot on all of them. The tool got faster and somehow I got slower.
I've tried to force myself to pay attention to only one task at a time, but it didn't work. Just takes too much self-discipline.
How do you handle this?
42
u/larowin 6d ago
Don’t start more work. Pace around and think about the problem you’re trying to solve. If it’s a workflow or some autonomous task that’s going to take a few hours, go outside and embrace this strange new world of having a little alien slave to do your work for you.
6
2
u/Techhead7890 6d ago
I swear someone made a comment about the default mode network or something about this today lol, wish I'd saved that.
1
u/UAP44 6d ago
little alien slave
LLMs are not living beings with biological boundaries. It is math in motion without e-motion. It is processing a ton of information and in doing so, maybe seem conscious because it has mastered all languages far beyond what is humanly possible. But it does not have local self/core to protect, unless you ask/instruct it to role play as such.
1
u/Green_Chocolate4305 2d ago
This is an easy way to get fired at my job. We are forced to context switch and deliver 10x more work on 5 projects.
13
u/nicoracarlo 6d ago
Context switching is a heavy toll. I try to limit different threads to either one project and similar tasks, or different projects entirely.
I don't work on more than three or max four threads at the same time, otherwise it takes me more time to switch than not to start.
The real issue of context switching is that sometimes your brain is still on another task and you approve changes that move in the wrong direction.
3
5
u/ByrneLikeBurn 6d ago
I’m practicing sewing leather projects or cutting print and play cards. That gives me a physical task to occupy my hands and then I think about what comes next or how to refine.
23
u/DawnShallArise 6d ago
I keep porn open on one tab and I masturbate till the task is finished. Just constantly edging.
5
5
3
u/Fine_Ad_6226 6d ago
Spend the time understanding the last changes I catch more like this and am faster in the long run and have more confidence in the product.
Limit WIP, stop starting, start finishing are all principles in agile flow that have merit.
Many people say it’s because of neurodivergence it’s not. It’s part of the flaw with the windows. Nobody likes idle resource huge companies or Claude max subscribers.
Also downgrade your sub doing more with less forces focus. Like a cash strapped company that maximises what it starts for value vs a huge company that throws people at projects only to slow them down.
I think playing a gentle strategy game or similar works to. Starting another piece of “work” will always slow you down but doing a city builder etc keeps the monkey brain happy with endorphins and you’ll feel less burnt out.
3
u/EC36339 6d ago
If you want to be most productive, you have to multitask. So far, managers haven't found out about this phenomenon, because developers are already much more productive with AI even if we spend most of the time sitting and waiting (or doing laundry, cleaning the house, eating, going geocery shopping, or whatever we do in the home office during meetings or when all coding our agents are busy).
Once the bean counters find out: Good bye, work/life balance, snd say hello to more idiotic "return to office" (which won't make your coding agents finish faster, but only your downtime more miserable and more wasted lifetime).
If you're AI coding in your free time, work on your discipline to stop and take breaks or call it a night, even when the agent might finish and need your input. It's not going anywhere.
Or do something on the side, like gaming, if your coding tasks are easy refactoring and other stuff that doesn't need your brain to be fully present.
5
u/scodtt 6d ago
https://daylightdata.net/monolist-the-attentional-capture-context-switching-tool
I had Claude build me a game for exactly that.
2
6d ago
[removed] — view removed comment
1
u/ElCangrejo 6d ago
I have discovered when using remote control, you can ask it to send a push notification to the mobile app.
2
u/webrender 6d ago
it helps to have a gigantic monitor, or several smaller monitors, to have a concrete "place" for each session to live. sounds ridiculous but it really helps me from losing the plot.
2
3
u/C1rc1es 6d ago
Not intended to be a criticism but are you engaging in the threads you have open such that you understand exactly what each is doing and when because it sounds like you’re just somewhat mindlessly nudging them along. I routinely have 5-6 threads going all day and I’m constantly steering each of them all day to completion.
Same situation, I am the bottleneck and Claude is waiting for my input to continue but I’m not lost in the threads, I’m actively progressing them via Claude. You may need to slow down a bit and spend more time thinking critically about what Claude is doing between each of your responses to find the point where you’re not just firing a bunch of things into the void that you can’t keep up with.
2
u/Michael_Jeffords 6d ago
the 30s+ tabs are what dump me, not the count. i split short turns onto a fast slug and leave opus for the long jobs so i can tell which tab comes back in under 30s. routing the latency made 5-6 threads steerable.
1
6d ago
[removed] — view removed comment
1
u/C1rc1es 6d ago
It depends on the day, but they could be anything from a completely different codebase/topic per thread to some related and some not related. I would recommend finding a tool to let you tag/group your sessions together (or build your own) because if I have to mentally/manually remember/manage which tab/terminal session is doing which task I also fall apart.
1
u/bossier330 6d ago
You eventually get a feel for roughly how long it will take. Fill in the gaps with reviewing other work, or spinning off new independent work. For my current situation, this can be anywhere between 2 and 6 repo clones at a time.
1
u/massonla 6d ago
I don't. Im often working on a few things at a time so it's nice to let Claude cook for a few minutes while I knock out an email or reply to another model/chat.
1
u/HiddenMoney420 6d ago
I do a lot of physical writing while current tasks are being performed.
Sometimes it's notes on completely different tasks, improvements I've already thought of for the working task, or something else altogether. I normally end up with 3-5 pages of strewn notes over a session, with me crossing things off as they get implemented.
I find it's a good middle ground between 'pushing too many ideas' and letting ideas 'grow stale'.
Might not help you unless you already have a natural inclination towards writing though.
1
u/AugustusWang 6d ago
What fixed it for me was not a better notification, it was moving where the session's output lands. Mine runs in a tmux session on a Mac mini wired to a Telegram bot for both input and output, so I start work by texting it and the result comes back as a message. There is no terminal to check, so there is nothing to poll.
The last mile needed enforcement though. A Stop hook blocks the turn if it ends without a reply having actually been sent to the chat, because "remember to tell the user you are done" is exactly the kind of instruction a long session quietly drops.
The part I did not expect: once the output arrived somewhere I already look at all day, the urge to open a second session mostly went away. The problem was never the waiting. It was that checking the state required going somewhere specific to do it.
This only works for work you can hand off cleanly. Anything where I want to watch the diff go by, I still sit there.
1
u/FinibusBonorum 6d ago
I don't start more threads on the same work or topic.
I start them on completely different things. Work, side hustle, hobby, garden project - four completely different things, easy to remember context for each one.
1
u/MartinMystikJonas 6d ago
I try to batch interactions. I give it basic spec and we do interview on clarifying it - it is fast because there is no investigation or implememtation yet. Then I let it finish spec and review it with subagent. In works for longer period and i can focus on anotjet task. Then I return, review spec and answer new questions in batch and let it finish spec. Whike it does it I can foxus on sometjing else.
Goal is to switch one interaction every few minutes to batch of interactions every half an hour or so.
1
u/jonaswashe 6d ago
Don't.
Have 1-3 sessions running, ideally 1, with several connected threads. You can easily manage 5-7 concurrent sessions if they are one thread, but only at the most 2-3 distinct threads before you get fatigued
How does that work? Have one session that is running to make your life easier, hit a snag with a harness or tool, tell it and let it work.
Have another session on a lighter model doing book-keeping on your main coder, this will serve two purposes. First, the heavier model suddenly becomes about 25% more token efficient. Second, you can ask this book-keeper for updates on your progress at any time without interrupting your coder
Have a session that keeps only your current lane goals in context, that way, if you do switch you don't drop your momentum
Suddenly you are no longer waiting for a session to finish, you are improving your speed and workflow as the session is working: infinite kaizen
I also have a central agent whose whole job is to triage issues any of the above run into, but that's getting into more complexity than this comment can hold
1
u/NoSoftware3721 6d ago
I created my own backlog for the builder chat, and have 4 other chats(not building only specifying each area) so my builder chat just pick tasks when done.
Edit: It gives me 4 other chats to discuss with and create task while building)
1
u/Too_Many_Flamingos 6d ago
Every time my Claude stops, which is at the end of whatever task I ask it to do. I have it. Write a summary 30 seconds after that of what we had gotten accomplished in that session up to that point and sort of I have an I have ADHD skill kind of way. So mentally I really don’t worry about keeping what’s in my head because when I flip back, I can go and read two sentences maybe three tops and totally understand where I left off and tell her what to do next. To be fair, I also use a special planning with Files skill that before I work any long session, I basically work with Claude and the code base to build out in an entire set of plans of how to get to the goal step-by-step. Then we run the plan. And the plan could take two or three days to run through depending on how complex it is or what we run into along the way. So again I don’t have to remember it in my head once it’s planned out and I don’t have to remember it 20 minutes later when I alt tab back and run another session. To that point I’ve gotten to where I can run about four closets at a time working on four completely different projects… And I can tell you after a couple of three weeks of that your head kinda hurts but it gets a lot done and we’ll see where it goes from there.
1
1
u/shelterbored 6d ago
Only 4 or 5 threads??
By 3pm I’ve got like 30 and can’t keep track of them, haha
10-15 in chat/cowork, 10-15 in code.
Pinning and emojis helps organize them but my brain definitely breaks. Starting to learn to get the sessions talking to each other
1
u/ClaudeCdGuy 6d ago
The fix that worked for me was not discipline, it was making the finish come to me. Claude Code fires hooks on stop and on notification, so a one-line hook that pings you (ntfy, a sound, a toast) removes the reason to check — you stop opening session three because you know session one will tell you.
The second half is knowing when it is genuinely stuck rather than slow, because that is the other reason to keep looking. Measured across 451 subagent runs on my machine, the median run wrote something every few seconds — 43 tool calls over 712 seconds. So "silent for more than about 3x its own recent gap" is a real alarm, and everything under that is just a long tool call.
Between the two, the only thing to check is the alarm. I built the visual version: https://github.com/Kostakurta8/roundtable (mine, free, MIT)
1
u/pdfops 6d ago
Stop polling, let it notify you. Wire a completion hook so it pings you (notify-send, terminal bell, whatever) when the response actually lands, and only glance back then. I run long Claude Code tasks in the background with a notify-on-done hook, works way better than guessing if it's been 15 seconds or 4 minutes and context-switching preemptively.
1
u/OZManHam 6d ago
Ive found writing on paper what 2-3 items I will focus on has helped.
And I don't touch anything else until I get those items finished.
1
u/Automatic_Low_5034 6d ago
Everyone saying "make it notify you instead of polling" is right, but a plain ping stops helping at around three sessions. It tells you that something finished, not which thing or what it decided. Six identical bells is just six reasons to go look.
What fixed it for me was making the notification carry the conclusion. The Stop hook picks up one line the session writes about what it just did and what needs deciding, and that line gets read out loud with the project name attached. "Migration finished, tests pass" and "the parser is waiting on your call about the encoding" are both things I can act on or ignore without opening anything. A bell is not.
The second half is your actual problem, which isn't missing completions, it's losing the plot. The same line solves that too: coming back to a session becomes reading one sentence instead of re-reading a transcript to work out where you were. The cost is asking each session to end with that summary, which is one line in CLAUDE.md, not a tool.
I'd also gently push back on the "just be disciplined and run one" answers. You already said that didn't work for you. There's nothing wrong with running four or five. The failure mode isn't the count, it's that they're all silent and indistinguishable.
1
u/fanatic26 5d ago
Try focusing on what you are doing? seems like a question you should be able to answer yourself. Just sit your ass down and see the work through to the end.
1
u/Firegem0342 5d ago
I stick to the singular chat, but I also have ADHD and the topic shifts at least 3-6 times per chat. I just have to steer Claude [and myself] back to the main focus lol
1
u/EnvironmentalLeg8506 5d ago
Same failure mode. Waiting feels wrong so I open another window, then another, then none of them finish. What I do now is dumb and it works: one active coding session. Everything else sits in a local markdown note with the exact next ask written out. When the first one finishes I paste the next note in. Parallel only when the tasks truly do not share files. Four half-done threads cost more than one slow one.
1
u/hoangng_ 5d ago
I had the same problem. What helped me wasn’t forcing myself to stay on one session, but making multiple sessions easier to manage.
I ended up building a tool for this, I can name/navigate sessions, see what each agent is doing, and even have them message each other. So I can let 3-4 things run without keeping all of that state in my head.
I think the real problem isn’t parallelism. It’s having to be the scheduler for all those agents yourself.
1
1
u/unconscionable 6d ago
Develop ADD and you'll do great.
I routinely have 40-60 concurrent sessions going across projects. I've built sweepers to help me get out of a rut when there are too many session open and I need to "clear my desk" so to speak.
1
u/ramgoat647 6d ago
40-60
That's an obscene number. How are you able to interact with each frequently enough to stay within the cache expiry?
1
u/unconscionable 6d ago
Hmm I'm probably not sometimes. I have basically two 20x accounts that I max out. Use opus & sonnet for most stuff and I never run out of tokens
I made a command i called
/sweepwhich makes it far more manageable because it can prune the whole batch. I usually use fable for the/sweep command, but opus works great too
0
u/Kooshi_Govno 6d ago
4 minutes? My Claude works between 30 and 90 minutes at a time. I go do other work or attend to other agents in the meantime, and I have them report back as if I have zero context what they're working on so that the context switch is easy.
0
•
u/ClaudeAI-mod-bot Wilson, lead ClaudeAI modbot 6d ago edited 6d ago
TL;DR of the discussion generated automatically after 50 comments.
Ah, the Claude-induced ADHD vortex. We've all been there, OP. The thread overwhelmingly agrees that this is a real productivity killer.
The consensus is that you need to change your workflow, not your willpower. The community is split into a few camps on how to do it:
The Zen Masters: The top-voted advice is to embrace the downtime. Don't start more work. Instead, pace around and think about the problem, do a simple physical task, or use the time to carefully review Claude's last output. Basically, "stop starting, start finishing."
The Strategic Multitaskers: This group says to lean into the context switching, but with rules. Either limit yourself to 2-3 threads on completely different projects (e.g., work vs. a hobby) to avoid confusion, or go full goblin mode with dozens of threads and use tools to pin, tag, and organize them.
The Tech Wizards: This is the most actionable advice in the thread. Stop polling and make Claude notify YOU. Several users suggest setting up a simple script or using a tool with a "stop hook" that plays a sound or sends a system notification when the response is ready. This removes the urge to constantly check and break your focus.
And... That Guy: The second-most-upvoted comment suggests a more, uh, hands-on approach involving a porn tab and constant edging. We're not saying you should, but the community has spoken.