# Team Tmux Pane Test ## Problem `teammateMode: "tmux"` is broken in Claude Code v2.1.117-119. Agents spawn as invisible background processes instead of getting their own tmux panes. This is a regression — tmux panes worked correctly on this machine through Sprint 35 (see `~/.claude/teams/sprint-35-*/config.json` for proof: `backendType: "tmux"` with real pane IDs). ## Relevant GitHub issues - https://github.com/anthropics/claude-code/issues/51818 — teammate CLI crash on permission_response - https://github.com/anthropics/claude-code/issues/52337 — subagent Ink rendering crash on Edit/Write ## Config (already set, do not change) - `.claude/settings.json` has `"teammateMode": "tmux"` and `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` - tmux is running, `$TMUX` is set, `TERM=tmux-256color` ## Version gate **Always start by looking up the release notes** for any versions between the last tested version and the current one. Check the GitHub releases page at `https://github.com/anthropics/claude-code/releases` for fixes related to teams, tmux, teammates, or the tracked issues below. If the release notes show no relevant fixes, log the version as SKIPPED (no relevant fixes) and stop — do not run the test procedure. **Check `claude --version` first.** If the version appears in the "Tested versions" log below, the bug was already confirmed broken on that release — do not re-test. Only run the test procedure on a version not yet logged. ### Tested versions | Version | Date | Result | |---------|------|--------| | 2.1.119 | 2026-04-25 | BROKEN — no tmux pane, no team config on disk | | 2.1.120–122 | 2026-04-30 | SKIPPED — release notes show no teams/tmux/teammate fixes; #51818 and #52337 still open (dupes of #51855, unreleased) | | 2.1.123 | 2026-04-30 | PARTIAL — tmux pane spawns, config on disk correct (backendType: tmux, paneId: %23). Custom subagent_type ("qatux") missing SendMessage — can receive but not send. General-purpose subagent_type has SendMessage — two-way comms work. BOTH types fail to process shutdown_request. TeamDelete reports success but does NOT kill the tmux pane — agent process keeps running, requires manual ctrl-c + exit. | | 2.1.123 (workshop) | 2026-04-30 | UPDATE — full workshop run with 4 general-purpose agents. Two-way comms confirmed for all. shutdown_request processed successfully by all 4 agents (contradicts earlier single-agent test). TeamDelete cleaned up correctly. Workaround: use general-purpose subagent_type with personality baked into prompt instead of custom subagent_type. | ## Test procedure 1. Check version: `claude --version` 2. If the version is already in the "Tested versions" table above, **stop here** — log nothing, do not spawn agents. Report that the version is unchanged. 3. Create a team and spawn one agent: ``` TeamCreate: team_name = "tmux-test" Agent: name = "qatux", subagent_type = "qatux", model = "sonnet", run_in_background = true, prompt = "You are a test agent. Message the team lead: 'tmux pane test — I am alive.' Then stay idle." ``` 4. Check: did a new tmux pane appear? Run `tmux list-panes -a` to verify. 5. Check: does `~/.claude/teams/tmux-test/config.json` exist and contain `backendType: "tmux"`? 6. Log the result in the "Tested versions" table above (version, date, BROKEN/FIXED + notes). 7. If BROKEN, clean up any leftover team state and stop. If FIXED, proceed to "Cleanup". ## Expected result (when fixed) - A new tmux pane opens with the Qatux session visible - Team config on disk shows `backendType: "tmux"` with a real pane ID - Agent is reachable via SendMessage ## Actual result (v2.1.119) - No tmux pane appears - No team config directory created on disk - Agent runs as invisible background process ## Context This blocks the generation-cascade workshop (ticket #897, Sprint 38). The full workshop has 3 participants (Gestalt, Tyre, Miri) + Qatux documenter, 3 rounds. Team and tasks are already created — once tmux panes work again, spawn the agents and go. See `docs/workshops/generation-cascade/BRIEF.md` for the full workshop brief. ## Cleanup Delete this file and `TeamDelete` the tmux-test team once the test passes.