Anthropic shipped a real dashboard for parallel Claude Code sessions this week. I spent a day with it, then rebuilt it here — keyboard and all — so you can scrub the workflow, hit the gotchas, and walk away knowing whether it changes how you work.
Six things changed how I use Claude Code after a day with agent view. Each chapter maps to a beat in the sim above. Click any card to jump the simulator there.
I stopped foregrounding everything.The old reflex was to keep Claude in front of me — partly to course-correct, mostly because watching it work felt productive. It wasn't. With agent view, I dispatch first and check in when a row turns amber. The first afternoon I shipped three things I'd been putting off because I “didn't have a clean block of time.” Async beats clean blocks.
I started treating needs_input as my only notification surface. Working rows can work. Failed rows want a postmortem, not a panic. Only amber means you. Once I stopped scanning the whole table every two minutes, I got my attention back.
I'm still skeptical that more visibility makes the agents more reliable. The dashboard solves a coordination problem, not a trust problem. Rob May was right about that. But the coordination problem was real, and it was eating my week. So: useful, not transformative — and a giant quality-of-life win the day it shipped.
The handful of shortcuts that actually changed my muscle memory, plus a copy-pasteable starter so you don't have to think about the first invocation.
@reviewer beats bare reviewer.↗ chapter