BrainBank
AI Classroom/AIClaude Code Deep Dive

ExitPlanModeTool: Exit Plan Mode

8/2/2026, 3:26:18 PM · Source

AI-translated on 8/2/2026, 3:27:16 PM · by Qwen3.6 35B (fast, default)

It’s Not “Ending the Plan”, But “Submitting the Plan”

The name ExitPlanModeTool can be misleading.
What it actually does isn't simply exiting, but rather:

Once the plan is written, submit it to the user for approval.

It represents the delivery checkpoint of Plan Mode, not just casually leaving the planning state.

Key Source Code

tools/ExitPlanModeTool/prompt.ts:

Use this tool when you are in plan mode and have finished writing your plan
to the plan file and are ready for user approval.

This prompt clearly spells it out:

  • First, write the plan file
  • Then call this tool
  • And request the user's approval

Call Chain

Completing the plan in Plan Mode > ExitPlanModeTool > Reading the plan file > Submitting for user approval > Returning to the implementation phase after approval

Its Boundary With AskUserQuestionTool

Anthropic has drawn a strict line for this boundary:

  • Unclear requirements: AskUserQuestionTool
  • Plan finished, seeking approval: ExitPlanModeTool

In other words:

Don't use a regular question tool to ask "is this plan okay?"

That's the responsibility of ExitPlanModeTool.

Why It Matters

Without this tool, Plan Mode easily degenerates into:

  • Writing out a bunch of plans
  • Then casually sending a sentence in natural language

With it in place, the system can treat "plan complete, awaiting approval" as a formal state.

Summary

The significance of ExitPlanModeTool lies in:

It turns the closing steps and approval process of the planning phase into a distinct state transition point within Claude Code.