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?
353 views
Replies
The re-entry cost is the part people underestimate the most in this thread. Getting pinged the moment an agent needs you handles the physical problem of finding the right pane. The harder problem is reloading what you were actually thinking before you switched away, and that cognitive reconstruction tax seems to be the real bottleneck here. Curious whether anyone's found something that actually shortens that part rather than just alerting faster.
@alex_gidirim
Totally agree — the cognitive reconstruction tax is the real bottleneck, way more than just finding the right pane. Was chatting with someone about this and they floated the idea of having the agent append a short "current task summary + next step" at the end of every output in the prompt. That way when you switch back, you just read that one-liner and you're back in context without having to scroll up and rebuild your mental model from scratch. Feels like a dirt-cheap trick that could cut re-entry friction by a lot.
Full disclosure: I've been tinkering on a tool called Poke Poke that tackles the other half — the physical "find the right terminal pane" problem via local hook notifications for Claude Code / Codex / Cursor. Doesn't solve the mental model rebuild at all, that's the much trickier piece. Still, if the pane-finding part is also annoying you, would love for you to give it a spin.
@hellokidder01 The task-summary idea is a quick fix worth trying. The slower piece is reconstructing your own reasoning from before you switched away, and a summary of the agent's state doesn't really touch that. Will give Poke Poke a look, thanks
Same problem, different flavor. I keep one pane pinned just for approvals so I'm not hunting across panes when it stops. Doesn't fix the 20 minutes lost before I actually look though.
@irahimiam
Fair point — pinning a pane solves the hunting, but it still depends on you remembering to look. That's exactly the gap PokePoke is built for.
When an agent stops for approval, you get a corner popup + an alert sound the moment it happens. The popup doesn't auto-dismiss — switch spaces, go grab coffee, come back, and it's still there waiting for you. No more "20 minutes later" moments. Click it (or press ⌘N) and you land on the exact pane that's waiting, so you don't even need the pinned-pane workaround anymore.
Treat them like interns. Start with sandbox + repetitive tasks, then edge cases, then 1% traffic.
The real bottleneck isn't the agent. It's our context switching.
Not just you. The 20 minutes isn't finding the pane, it's the context you drop while away, so notifications alone never fixed it for me. Two things did: pinning each agent to its own desktop space so switching is one keystroke, and eventually building an iPhone app (Remote Mac) that mirrors my Mac with a trackpad and keyboard, so "yes, option 2" happens from the couch or the grocery line instead of a walk back to the desk. The agents wait for me a lot less now.
Left an agent to fix the failing test while I stepped away. The suite was green so I kept moving. And days later I found out it "fixed" it by weakening the assertion instead of fixing the code ) Plus the minutes lost waiting are nothing compared to the hours debuging false confidence
Real cost was rushing approval to unblock terminal. Skimmed diff and shipped report with confident number nobody measured. And took full day to trace issue and realize agent just hardcoded placeholder value )
the tax i managed to cut wasnt the finding, it was the asking. most of the yes prompts i was answering werent really decisions, they were the agent checking in on things id have approved every time without thinking about it. so i wrote the approvals down once, as an allowlist of operations it can run unattended, and left the gate on only the things that are genuinely irreversible. the interrupt count dropped a lot, and the ones that survived are actually worth getting up for. notification routing is a real fix and pokepoke sounds genuinely useful for the ones that remain. i just found the bigger win sat upstream of it, getting the count down rather than answering the same question faster.