Repository navigation
Diagnose: teammates get Agents & shells rows that never end #235
Description
Question
Why does a teammate (CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1) get an Agents & shells row (◐ teammate · …) and a "teammate started" toast, and why does the row stay running after TaskStop? MEMORY.md says teammates are filtered out.
Reproduce it live on 2.1.292 under the map's Notes, at release/0.5.0 and at v0.4.0, and find the root cause.
Resolve with one of:
- ctui bug: a new ready-for-agent fix ticket (child of the map, label
ready-for-agent) in the shape of "Sidebar glass draws light grey under tmux without truecolor": what happens, why, the ask, the test seam, and abugfix/<name>branch cut fromrelease/0.5.0with its pull request into it. - Engine limit ctui can't work around: a new
wayfinder:grillingchild ticket putting defer-to-0.6.0 vs drop to the human, with the evidence.
If the engine moved since a MEMORY.md entry was checked, say which entry is stale.
Activity
a1exk-dev commentedon Oct 9, 2026
Resolved: this is a ctui bug, present since v0.4.0. Fix ticket: Teammates get Agents & shells rows and toasts from agent.spawn.
I reproduced it live on 2.1.292 at
release/0.5.0and atv0.4.0. A named Agent call drew◐ teammate · Sleep 60 then reply…with└ ◐ $ sleep 60under it. Both rows were stillrunningpast 1 minute, after the model's TaskStop reportedstopped.Root cause: on 2.1.292 a teammate fires
agent.spawnwithisTeammate: trueandsubagentType: 'teammate'(from a tagged probe, and also in the vendored types). The spawn hook adds the row and the toast. The list filter then hides every status change for that row. TaskStop returns the teammate's task id (tin1b73zq,in_process_teammate), not the spawn'sagentId, so the TaskStop hook doesn't end the row.Stale memory: MEMORY.md "A Workflow run is one task row; teammates stay hidden" says teammates fire no
agent.spawn. The fix ticket rewrites it.