[{"data":1,"prerenderedAt":100},["ShallowReactive",2],{"page-\u002Fteam-featurerequest":3},{"id":4,"title":5,"body":6,"date":88,"description":89,"extension":90,"image":91,"kind":92,"meta":93,"navigation":94,"order":95,"path":96,"seo":97,"stem":98,"__hash__":99},"content\u002Fteam-featurerequest.md","feature-request @anthropic — the Bobs go public",{"type":7,"value":8,"toc":84},"minimark",[9,18,26,50,67,78,81],[10,11,12,13,17],"p",{},"By the end of May I wasn't running an assistant anymore. I was running a ",[14,15,16],"strong",{},"team"," — 8 to 13 Claude Code agents in parallel on the same codebase, each with its own name and job.",[10,19,20,21,25],{},"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 ",[22,23,24],"code",{},"frontend_helper_v2",".",[10,27,28,29,32,33,36,37,41,42,45,46,49],{},"So on May 29 I did the obvious thing — I wrote it up and sent Anthropic a feature request. Not a wish-list: a ",[14,30,31],{},"field report"," from a setup that already worked. The heart of it: give agents ",[14,34,35],{},"stable names that map to roles"," (the backend agent stays ",[38,39,40],"em",{},"the same agent",", project after project, instead of a fresh helper every init), and a ",[14,43,44],{},"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 ",[22,47,48],{},"team.yaml"," lineup, a two-way inbox, native path-ownership.",[51,52,53],"nerd",{},[10,54,55,56,59,60],{},"I was solving it outside the tool with embarrassingly simple parts — ",[22,57,58],{},".log"," files, a bash heartbeat helper, a tiny Nuxt dashboard polling every 3 seconds. It just worked. The request was basically: this pattern wants to live closer to the CLI. → ",[61,62,66],"a",{"href":63,"rel":64},"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-code\u002Fissues\u002F63415",[65],"nofollow","issue #63415",[10,68,69,70,73,74,77],{},"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 ",[14,71,72],{},"first time the Bobs went public."," (And yes, the names come from Dennis E. Taylor's ",[38,75,76],{},"Bobiverse",". If you haven't read them: fix that. :))",[10,79,80],{},"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.",[10,82,83],{},"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.",{"title":85,"searchDepth":86,"depth":86,"links":87},"",2,[],"2026-05-29","May 29: I sent Anthropic a field report from running a real team of named Claude Code agents — stable naming + a live stand-up. The first time the Bobs left my machine and went public.","md",null,"challenge",{},true,3,"\u002Fteam-featurerequest",{"title":5,"description":89},"team-featurerequest","KmxJrKqg5WjGAmJfV3gdycs0wegc40liyOjcLGwRbLo",1782576224704]