Agent teams permission routing crashes CLI on teammate tool approval (regression in 2.1.111)

Summary

With CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1, whenever a teammate requests
permission for a tool (e.g. Write), the permission request is routed to the
team leader — and the CLI crashes at that point. This is a full blocker: no
agent-team work can proceed on 2.1.111+.

Regression window

| Version | Published | Status |
|---------|-----------|--------|
| 2.1.110 | 2026-04-15 | ✅ works |
| 2.1.111 | 2026-04-16 | ❌ crashes |
| 2.1.112 | 2026-04-16 | ❌ crashes |

So the regression landed in 2.1.111. Note this is independent of the
Opus 4.7 model release on 2026-04-16 — the crash is harness-side and
reproduces with Opus 4.6 and Sonnet 4.6 as well.

Environment

• Claude Code: 2.1.112 (same behaviour on 2.1.111)
• OS: macOS Darwin 25.3.0, arm64
• Install: native (~/.local/share/claude/versions/)
• Shell: zsh
• Env flags: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
• Settings: skipDangerousModePermissionPrompt: true, hooks configured on

SessionStart and PostToolUse (mentioned in case relevant)

Repro

1. TeamCreate a team
2. Spawn a teammate via Agent with team_name + name
3. Teammate calls Write (or any tool needing permission)
4. UI shows: "Permission request sent to team '<name>' leader"
5. CLI crashes at that moment — leader never receives an approvable prompt

What doesn't fix it

• Passing mode: "bypassPermissions" on the teammate Agent spawn — still

crashes. Suggests teammate-side mode is not being respected before the
routing step runs.

• Setting defaultMode: "bypassPermissions" plus an exhaustive allow list

in .claude/settings.local.json — teammates don't consult the user's
allow-list, they consult the leader, and that round-trip is what crashes.

• Granting macOS Full Disk Access to the terminal.
• Removing skipDangerousModePermissionPrompt.

Workaround

Pin to 2.1.110 and disable the auto-updater:

ln -sfn ~/.local/share/claude/versions/2.1.110 ~/.local/bin/claude

Plus DISABLE_AUTOUPDATER=1 in ~/.claude/settings.json env block.

Impact

Agent teams is the primary multi-agent workflow for users who have built
around the experimental feature over the last few months. Any version
≥2.1.111 is unusable for team-based work until this is fixed, regardless
of which model is selected.

Asks

• Fix in a 2.1.x patch
• If there's a crash log / session dump location I should attach, happy to

reproduce and share

• Consider treating the teammate→leader permission round-trip as a

bypass target so mode: "bypassPermissions" on the teammate spawn
short-circuits the routing entirely