New Claude Code Mod… it keeps getting more hackable and customizable This Mod lets you see every subagent running in your session You won’t lose track of them anymore... they stay visible in the sidebar, where you can review what each one has done and how much context it... has used Install it with one command: npx claude-code-templates@latest --mod ui/agent-flow Link:show more

we had the same subagent sprawl problem. our receipt prints child id, cwd, tool route, and last error after each handoff, then kills the child after two identical failures. does the sidebar expose the failed tool call too?

one more state worth showing: landed. a subagent that finished but never merged its result is the one still holding context while every status view reads green. the orphan is the leak.

I added a similar board to keep tracking on tasks and agents

sidebar visibility only helps if you can tell a stuck one from a working one at a glance. is the row just a name, or do you get last tool plus elapsed?

Finally, a sidebar to watch the subagents I forgot I spawned quietly burn through my context.

a subagent comes back with a thin answer and you can't tell if it ran out of room or just didn't find anything. seeing the context it used while it still runs saves that rerun. mostly that means long sessions. the ones where you stop keeping count.

So real

Daniel - how many agents before the sidebar gets noisy?

Seeing subagents in the sidebar helps me understand what’s running. I also want the result to stay central while I ask the agent about a decision. We sketched that layout in July; “New side chat” brought me back to it:

侧栏除了看 token 用量，能直接标出子代理当前正在调用的 tool call 和挂起耗时吗？排查卡住的时候一目了然最有用。

侧边栏把子代理都摊开，调试起来舒服多了

need that context-used panel before I kill every subagent again

In the mod's source, Workflow agents don't fire agent.spawn, so they hang flat off main as 'loop' rows with the prompt marked not seen. Does the engine hand you a run id you could nest them under?

Oh this is what I needed. I lose track of subagents constantly and just end up killing all of them.

thats pretty nifty - when do you find yourself using this?