Permission prompt UI crashes and dumps minified source when teammate requests approval (tmux + iTerm2)
Environment
- Claude Code version: 2.1.112
- OS: macOS (Darwin 25.4.0)
- Terminal: iTerm2
- Multiplexer: tmux 3.6a
- Shell: zsh
Summary
When using a team of agents, if a teammate agent requests approval from the teamlead, the approval prompt UI crashes. Instead of rendering the [C] / [X] decision prompt, Claude Code dumps a large chunk of minified source from cli.js into the terminal.
Note: team agents spawn inside tmux panes by design, so "don't use tmux" is not a viable workaround for team mode — the bug effectively blocks any teammate→teamlead approval flow.
Repro
- Start a team session in iTerm2 (team agents spawn into tmux panes automatically).
- Have a teammate agent (e.g.
vs-wave-0) request approval from the teamlead. - Observe the terminal: instead of a prompt, raw minified JS is printed, ending with a stack trace.
Expected
A normal [C] / [X] approval prompt renders in the teamlead pane.
Actual
Message shown: ⏺ vs-wave-0 terminated. Awaiting your [C] or [X] decision before followed by a large dump of minified code from cli.js (functions L_6, tI5, ql7, eI5, By, _x5, qx5, $x5, v_6, Tl7, etc.), then a stack trace:
-<anonymous> (/$bunfs/root/src/entrypoints/cli.js:8231:15642)
-qX (/$bunfs/root/src/entrypoints/cli.js:477:63169)
-sPH (/$bunfs/root/src/entrypoints/cli.js:477:76220)
-ov (/$bunfs/root/src/entrypoints/cli.js:477:76101)
-sPH (/$bunfs/root/src/entrypoints/cli.js:477:76199)
-ov (/$bunfs/root/src/entrypoints/cli.js:477:76101)
... (sPH/ov recursion repeats)
The recursion between sPH and ov in the permission-prompt render path looks like the actionable signal. The permissionExplainerEnabled / Uf8() branch also appears in the crashing region.
Notes
- Happens specifically on teammate → teamlead approval prompts.
- Suspected tmux/Ink rendering interaction — possibly narrow pane width triggering the render recursion.
- Blocks team-mode workflow since teammate agents always run inside tmux.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗