Agent Teams: teammate tmux panes crash with React Ink rendering error

Bug Description

When using Agent Teams (CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1), teammate agents spawn tmux panes that crash shortly after starting. The panes either:

1. Appear briefly as split panes, then become unresponsive (can't click/switch between them)
2. Die entirely, leaving only the lead agent's session

The agents themselves do work (file edits succeed before the crash), but the tmux pane UI crashes with a React Ink rendering error.

Stack Trace

createInstance (/$bunfs/root/src/entrypoints/cli.js:502:249)
PL (/$bunfs/root/src/entrypoints/cli.js:484:58456)
LYH (/$bunfs/root/src/entrypoints/cli.js:484:88642)
rZH (/$bunfs/root/src/entrypoints/cli.js:484:87842)
RD6 (/$bunfs/root/src/entrypoints/cli.js:484:8673

Also observed minified React Ink component code in the crash output:

if(_[25]!==D||_[26]!==b||_[27]!==S)B=sj9.default.createElement("ink-text",{style:b,textStyles:S},D)...

Steps to Reproduce

1. Enable agent teams: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in settings
2. Run Claude Code inside tmux (iTerm2 + tmux integration)
3. Create a team with TeamCreate
4. Spawn 2-3 teammates with Agent tool using team_name parameter
5. Panes appear briefly then crash or become unresponsive

Observed Behavior

• Teammate panes are registered in the team config.json with valid tmuxPaneId values
• tmux list-panes -a shows only the lead agent's pane; teammate panes are gone
• SendMessage to teammates returns "No agent named 'X' is currently addressable"
• Respawning teammates repeats the crash cycle
• Spawning agents WITHOUT team_name (as background agents) works reliably — they complete their work but have no visible UI

Environment

• Claude Code: 2.1.119
• tmux: 3.6a
• macOS: 26.3.2 (Tahoe)
• Terminal: iTerm2 with tmux integration
• Node: v24.3.0
• Model: Claude Opus 4.6 via AWS Bedrock
• Settings: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in both project and user settings
• Agent mode: bypassPermissions

Expected Behavior

Teammate agents should persist in their tmux panes and remain interactive for the duration of their work.

Workaround

Using the Agent tool with run_in_background: true (without team_name) works reliably for parallel agent work, but loses the split-pane visibility that agent teams provide.