By the end of May I wasn't running an assistant anymore. I was running a team — 8 to 13 Claude Code agents in parallel on the same codebase, each with its own name and job.
And running it, I kept hitting the same four walls: I couldn't reliably tell who was doing what; five silent minutes felt like "everything's dead, restart it"; once a sprint ended the trail was gone; and every init spawned yet another half-redundant frontend_helper_v2.
So on May 29 I did the obvious thing — I wrote it up and sent Anthropic a feature request. Not a wish-list: a field report from a setup that already worked. The heart of it: give agents stable names that map to roles (the backend agent stays the same agent, project after project, instead of a fresh helper every init), and a live stand-up — one browser tab showing who's doing what, who's blocked, what actually happened. Plus a handful of CLI-native wishes that fell straight out of running the thing: persistent agent identity, a built-in heartbeat stream, a team.yaml lineup, a two-way inbox, native path-ownership.
A small moment with a big meaning for me. After almost 20 years I'd basically never posted anything, anywhere — I just did the work. This was the first time the Bobs went public. (And yes, the names come from Dennis E. Taylor's Bobiverse. If you haven't read them: fix that. :))
Then — maybe two days later — there it was: every agent in the lineup had picked up a little status line at the bottom of the CLI — idle or busy, and how long since its last heartbeat. If you're running a team yourself, that's where you'll spot it now, right at the bottom of Claude Code; you can even see roughly what each agent is doing, click in, and drop straight into its context. A built-in heartbeat stream and a live stand-up — which, two days earlier, was more or less exactly what I'd written up.
Now, I won't oversell it. Claude Code ships updates at a frankly absurd rate, and this one just showed up with the next one — so I genuinely don't know whether my report nudged anything or the feature was already in the oven. Probably the latter. But that's the part I keep coming back to: the tool I'm building this whole team on gets visibly better, week over week, at a pace that's hard to keep up with. And I find that fascinating.
