Your AI agent is waiting for you. Your attention isn't. How much time do you lose to this?
by•
Daily reality: Claude Code in one pane, Codex in another, Cursor in a third, plus a few shells. An agent stops and waits for "yes". By the time I find the right pane, 20 min gone.
Just me? What's your setup — notifications, layout tricks, or you've accepted the tax?
165 views
Replies
I stopped scanning panes and gave each agent its own sound — one chime for "needs a decision," another for "done," a third for "approve this prompt" — so I can stay heads-down on a second machine and only turn around when the one that actually needs me goes off. For me the 20 minutes was never the waiting, it was the cost of switching over just to check; once the sound tells you which agent and why, that mostly disappears.
@urvault
Legitimately good setup — and you named the real cost precisely: "switching over just to check" is the tax that keeps hurting.
A few limits I see, though: the sound-mapping starts to fight you past ~4 agents × 3 event types, and even when the chime tells you which agent, you still have to physically get to that pane — that "last mile" is where a lot of friction hides when you're juggling panes on one machine.
Also honest question — when you're deep in focus mode, does the sound ever just… not register? I've noticed the deeper I go, the more my brain filters out ambient audio, especially with music or noise-canceling headphones on. Sound works great as an "alert layer" until the moment you actually need it most.
How many agents are you running when this really shines?
Honestly, the ideal workflow is agents running in parallel and only interrupting for genuinely important decisions. Approving every tiny step kills the flow.
@aleksander_brousseau Agreed on the ideal — though in practice I've found even a well-tuned approval policy still surfaces enough interruptions that catching them matters. The two problems compound rather than replace each other.
I usually pin the most active agent beside my editor. That simple layout change reduced searching time. Maybe a dedicated approval dashboard could improve this even more.
@donna_gerrard Pinning works when there's clearly one "main" agent, but breaks the moment you have 3+ running — which pane gets the prime spot? A dashboard has the same tradeoff: still pull, you still have to look.
Also honest question — with agents this capable, can you really sit beside one "main" pane and just wait for it to finish? I always end up spinning off two more tasks in the meantime, and then the "main" one isn't really main anymore.
Me thinking operating systems could treat waiting agents like urgent messages instead of ordinary windows. Faster visibility would reduce wasted attention. Would you use a feature like that?
@jason_scott8
Honestly the OS does already have this — push notifications with priority tiers exist on both macOS and Windows. The gap isn't the OS layer, it's that no single app has a reason to identify "this specific agent is waiting on approval" as an event worth priority-notifying about.
Which is why this ends up being a userland problem — someone has to sit between the agents and the OS notification system, translate "agent stopped mid-tool-call" into "urgent ping", and route it back to the right pane. OS won't do that for you because it can't tell a waiting agent from a background service that's just idle.
So yeah, I'd use that feature. I'd argue it already has to exist, just built by someone at the application layer rather than by Apple or Microsoft.
I'm very new to it all, completely lost but loving it. so far iv managed to pull together a few basic desktop apps , all worthless but still fun to build. And yes I am completely lost with the platforms and what they are actually doing most the time. and then the dreaded updates :)
@fred_jones6 Ha, "lost but loving it" is honestly the ideal state to be in — most of the fun is in that phase before things start feeling like work. Keep building the worthless ones, that's how the good instincts show up.