[DOCS] Undocumented "Clear Context" transition options in Plan Mode

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/common-workflows#use-plan-mode-for-safe-code-analysis

Section/Topic

The "Use Plan Mode for safe code analysis" section in docs/en/common-workflows.md. Specifically, the transition step where the user approves the plan to begin coding.

Current Documentation

Currently, the documentation explains how to enter plan mode and iterate, but skips the menu interaction for exiting/executing the plan.

Example: Planning a complex refactor ``bash claude --permission-mode plan ` ` > I need to refactor our authentication system to use OAuth2. Create a detailed migration plan. ` Claude analyzes the current implementation and create a comprehensive plan. Refine with follow-ups: ` > What about backward compatibility? > How should we handle database migration? ``

It does not document the menu options presented when Claude calls ExitPlanMode.

What's Wrong or Missing?

When Claude finishes a plan and presents it to the user, the CLI offers specific menu options to transition into execution mode. There is a specific option "Yes, clear context..." which is currently undocumented.

This is a critical feature because it allows the user to wipe the conversation history (saving tokens/context window) while retaining the approved plan file for execution.

The menu options differ based on how the session was started:

1. Standard Session: Displays 1. Yes, clear context and auto-accept edits
2. Dangerously Skip Permissions: Displays 1. Yes, clear context and bypass permissions

Additionally, this "Clear Context" feature is currently CLI-only and does not appear in the VS Code extension, which should be noted.

Suggested Improvement

Add a subsection titled "Executing the Plan" under "Use Plan Mode for safe code analysis".

Suggested Text:

Executing the Plan

When Claude finishes the plan, it will present a menu to proceed with implementation. You will see an option to "Clear context":

Would you like to proceed?

❯ 1. Yes, clear context and auto-accept edits
  2. Yes, and manually approve edits
  3. Yes, auto-accept edits
  4. Yes, manually approve edits
  5. Type here to tell Claude what to change

"Yes, clear context" is recommended for long planning sessions. It clears the conversation history to free up context window space, but retains the plan file and the context of the files Claude needs to edit.

Note: The "Clear context" option is currently available only in the CLI, not the VS Code extension.

Permission Modes:

• If you are in standard mode, Option 1 will switch to Auto-Accept Edits.
• If you started the session with --dangerously-skip-permissions, Option 1 will display "Yes, clear context and bypass permissions".

Impact

High - Prevents users from using a feature

Additional Context

Scenario 1: Standard Session

 Would you like to proceed?

 ❯ 1. Yes, clear context and auto-accept edits (shift+tab)
   2. Yes, and manually approve edits
   3. Yes, auto-accept edits
   4. Yes, manually approve edits
   5. Type here to tell Claude what to change

Scenario 2: Session started with --dangerously-skip-permissions

 Would you like to proceed?

 ❯ 1. Yes, clear context and bypass permissions
   2. Yes, and manually approve edits
   3. Yes, and bypass permissions
   4. Yes, manually approve edits
   5. Type here to tell Claude what to change