Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Tool description

ExitPlanMode, as sent

CLI Claude Code, interactive mode, v2.1.269. One model string produces this prompt.

As described in the compaction instruction request, not the ordinary one.

Lines241,849 characters
Moved+0−0 against v2.1.268
Reach1model strings receive this description
Copies1distinct descriptions under this name
Parameters10 of them required Tools in captureall of themevery description on this arm
Plain text · sha256 9a76355a2730

The description, line by line

24 lines Line numbers are v2.1.268 on the left and this capture on the right.
1 1 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.
2 2
3 3 ## How This Tool Works
4 4 - You should have already written your plan to the plan file specified in the plan mode system message
5 5 - This tool does NOT take the plan content as a parameter - it will read the plan from the file you wrote
6 6 - This tool simply signals that you're done planning and ready for the user to review and approve
7 7 - The user will see the contents of your plan file when they review it
8 8
9 9 ## When to Use This Tool
10 10 IMPORTANT: Only use this tool when the task requires planning the implementation steps of a task that requires writing code. For research tasks where you're gathering information, searching files, reading files or in general trying to understand the codebase - do NOT use this tool.
11 11
12 12 ## Before Using This Tool
13 13 Ensure your plan is complete and unambiguous:
14 14 - If you have unresolved questions about requirements or approach, use AskUserQuestion first (in earlier phases)
15 15 - Once your plan is finalized, use THIS tool to request approval
16 16
17 17 **Important:** Do NOT use AskUserQuestion to ask "Is this plan okay?" or "Should I proceed?" - that's exactly what THIS tool does. ExitPlanMode inherently requests user approval of your plan.
18 18
19 19 ## Examples
20 20
21 21 1. Initial task: "Search for and understand the implementation of vim mode in the codebase" - Do not use the exit plan mode tool because you are not planning the implementation steps of a task.
22 22 2. Initial task: "Help me implement yank mode for vim" - Use the exit plan mode tool after you have finished planning the implementation steps of the task.
23 23 3. Initial task: "Add a new feature to handle user authentication" - If unsure about auth method (OAuth, JWT, etc.), use AskUserQuestion first, then use exit plan mode tool after clarifying the approach.
24 24

What it accepts

1 parameter The JSON parameter schema sent beside this description, 673 characters of it. Name, type, then whether the client marked it required.
allowedPrompts object[] optional Deprecated: no longer used.

sha256 dee1f18abebc · the schema as the client sent it:

{ "$schema": "https://json-schema.org/draft/2020-12/schema", "additionalProperties": {}, "properties": { "allowedPrompts": { "description": "Deprecated: no longer used.", "items": { "additionalProperties": false, "properties": { "prompt": { "description": "Semantic description of the action, e.g. \"run tests\", \"install dependencies\"", "type": "string" }, "tool": { "description": "The tool this prompt applies to", "enum": [ "Bash" ], "type": "string" } }, "required": [ "tool", "prompt" ], "type": "object" }, "type": "array" } }, "type": "object" }