Teammates don't inherit bypassPermissions from parent session

Description

When the parent/lead session has bypass permissions enabled (via shift+tab toggle), spawned teammates do not inherit this permission mode. The teammate prompts for permissions on tool calls despite the parent having bypass permissions on.

Expected behavior

Per the docs:

• agent-teams.md: "Teammates start with the lead's permission settings. If the lead runs with --dangerously-skip-permissions, all teammates do too."
• sub-agents.md: "If the parent uses bypassPermissions, this takes precedence and cannot be overridden."

Teammates should inherit bypassPermissions from the parent session.

Actual behavior

Teammate spawned via the Agent tool (with run_in_background: true) does not inherit bypass permissions. The teammate's session shows permission prompts for file reads and other operations.

Environment

• Claude Code v2.1.92
• macOS (Darwin 25.2.0)
• Running in tmux (may be relevant — user reports this works fine outside tmux normally)
• Opus 4.6 (1M context), Claude Max
• Bypass permissions toggled on via shift+tab in the parent session

Steps to reproduce

1. Start a Claude Code session
2. Toggle bypass permissions on (shift+tab)
3. Create a team with TeamCreate
4. Spawn a teammate via Agent tool with run_in_background: true
5. Observe that the teammate's pane does not show "bypass permissions on" and prompts for permissions

Notes

The bypass permissions was set via the interactive shift+tab toggle, not via --dangerously-skip-permissions CLI flag. It's possible the inheritance only works with the CLI flag and not the interactive toggle. If so, the docs should clarify this distinction.