You'll notice
Exiting plan mode inside a team context submits your plan to the team lead's inbox for approval instead of just switching modes.
Exiting plan mode inside a swarm/team context can now submit the plan for approval instead of just switching modes: ExitPlanMode writes a plan_approval_request message to the team lead's inbox and returns an awaitingLeaderApproval state, showing "Your plan has been submitted to the team lead for approval."
Names in the bundleExitPlanMode
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Create custom subagents touched a line naming ExitPlanMode after this was published.
The second filter applies to subagents running in the background. Apart from `Agent` and `ExitPlanMode`, which follow the first filter's conditions wherever the subagent runs, a background subagent keeps every MCP tool but only these built…sub-agents see the edit
Confirmed since
Anthropic's documentation has since written up ExitPlanMode, on Hooks reference.
In [non-interactive mode](/docs/en/headless) with the `-p` flag, Claude Code offers `AskUserQuestion` and `ExitPlanMode` only when the run has a [permission host](/docs/en/headless#turn-off-permission-prompts-in-unattended-runs) to receive…hooks see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up ExitPlanMode, on Hooks reference.