Key takeaways
- Only 10% of interrupted programming sessions resume within a minute; fragmentation lowers measured output.
- Agent approval requests are unpredictable, brief and blocking: the costliest kind of interruption.
- Move the ask to the wrist so it can be answered without leaving what you were doing.
Agentic coding changed the shape of a developer's day. The agent works for minutes at a time, then stops and asks. Every one of those asks is an interruption, unless it arrives somewhere you can answer without leaving what you were doing.
What interruption costs a programmer
Parnin and Rugaber analysed 10,000 recorded programming sessions from 86 developers and surveyed 414 more. Only 10% of interrupted sessions resumed productive editing within a minute; most needed a period of re-navigation first. Meyer and colleagues instrumented 20 professional developers for eleven workdays and found that work fragmentation correlated with lower observed productivity, and that longer switches made it worse. Gloria Mark's broader office studies put the average refocus cost of an interruption at about 23 minutes.
Why agents make it worse before they make it better
An agent that needs your approval every few minutes produces the worst kind of interruption: unpredictable, brief, and blocking. You cannot leave the desk, because it might ask; you cannot fully engage with something else, because it will ask. The productive time the agent saves is paid back in supervision.
Moving the ask to the wrist
The interruption cannot be removed; an agent that never asks is an agent you should not run. What can change is where the ask lands and how much it costs to answer. A request that arrives on your wrist, with the tool and its arguments in front of you, is answered in the time it takes to read a sentence and tap. You were in the kitchen, or in a meeting, or on a walk, and you stayed there.
What PeakWatch does with it
PeakWatch ranks your sessions by which one is blocked on you, shows every permission request with its arguments and the SDK's reason, and lets you approve, deny or ask why in one tap. Ignore it and the request denies itself when the countdown ends. The sessions keep running on your machine; the interruptions stop owning your location.
PeakWatch is built for this
Your coding agent, on your wrist. Coming soon, free during the beta.
Questions
Does answering from a watch really avoid the context switch?
What if I am mid-thought on something else?
Is this only for Claude Code?
Sources
- Parnin C., Rugaber S. (2011). Resumption strategies for interrupted programming tasks. Software Quality Journal. https://link.springer.com/article/10.1007/s11219-010-9104-9
- Meyer A.N. et al. (2014). Software developers' perceptions of productivity. FSE. https://dl.acm.org/doi/pdf/10.1145/2635868.2635892
- Sanchez H. et al. (2015). An empirical study of work fragmentation in software evolution tasks. SANER. https://ieeexplore.ieee.org/document/7081835/