Skip to content
← Back to release · 2.1.299
New features / v2.1.299

Plan mode bypass permissions notice

CHANGELOG · original

Added a one-time note when plan mode won't ask before most edits or commands because bypass permissions is available
Open official changelog ↗

Documentation

Documentation excerpt

Analyze before you edit with plan mode

Plan mode tells Claude to research and propose changes without making them. Claude reads files, runs shell commands to explore, and writes a plan, but does not edit your source. Except in interactive terminal sessions with bypass permissions available, edits stay blocked until you approve the plan.

What happens to a shell command during planning depends on the session, and the first of these cases that matches applies:

  • Interactive terminal sessions with bypass permissions available: neither the classifier nor a prompt applies to planning commands. Skip all checks with bypassPermissions mode covers the few things that still prompt there.
  • Auto mode available and the useAutoModeDuringPlan setting on, which it is by default: the classifier reviews shell commands other than critical-path removals instead of prompting you. Approved commands run, and rejected ones are blocked.
  • Auto mode not available, or useAutoModeDuringPlan off: commands outside the built-in read-only set prompt for approval, including when the sandbox's auto-allow mode is enabled.

Enter plan mode by pressing Shift+Tab or prefixing a single prompt with /plan. You can also start in plan mode from the CLI:

claude --permission-mode plan

With no approval prompt open, press Shift+Tab again to leave plan mode. At the approval prompt, press Esc first, since pressing Shift+Tab there approves the plan.

Review and approve a plan

When the plan is ready, Claude presents it and asks how to proceed. From that prompt you can choose:

  • Yes, and use auto mode: approve and start in auto mode. If auto mode isn't available to your session, for example because your organization turned it off, this option reads Yes, auto-accept edits. If you started the session with bypass permissions enabled, the option reads Yes, and switch to BYPASS PERMISSIONS (no further prompts) for this session instead.
  • Yes, manually approve edits: approve and review each edit individually.
  • No, keep planning: stay in plan mode and tell Claude what to change.

Approving a plan exits plan mode and switches the session to the permission mode each approve option describes, so Claude starts editing. To plan again, cycle back to plan mode with Shift+Tab, or prefix your next prompt with /plan.

Press Ctrl+G to open the proposed plan in your default text editor and edit it directly before Claude proceeds. When showClearContextOnPlanAccept is enabled, the list gains a first option that approves the plan and clears the planning context.

Accepting a plan also gives the session a generated title based on the plan, unless you've already named the session.

Set plan mode as the default

To make plan mode the default for a project's terminal sessions, set defaultMode to plan in .claude/settings.json, placed as the example under Start in a different permission mode shows. Conversations the VS Code extension starts don't read project settings for the starting permission mode. There, set claudeCode.initialPermissionMode to plan in your VS Code user settings instead.

Documentation snapshot · 2026-11-20

Change details