Claude Code's Plan Mode: review before anything runs

The mode that plans without executing — how to switch, and when to use it.

What Plan Mode is

A mode where Claude Code investigates your codebase read-only and presents a plan — without writing files or running commands. You review/adjust it, then switch to a normal mode to execute.

How to switch

`Shift+Tab` cycles through modes (ask-before-edits → auto-edit → plan). To start directly in Plan Mode, use `--permission-mode plan` (a real choice confirmed via `claude --help` on this Mac).

$ claude --permission-mode plan

What does and doesn't happen

No file writes or shell execution occur. Claude investigates with read-only tools and presents its intended approach as text; a human decides whether to proceed.

When to use it

For large, hard-to-scope changes or anything near production, plan first to catch unintended scope before it runs. For small, safe fixes, it can feel like overhead.

vs hooks and permissions

Plan Mode is a human-driven pause; PreToolUse hooks and permissions.deny are deterministic, always-on blocks for specific conditions. Combine both for extra safety.

A practical combo

Default to acceptEdits for speed, switch to Plan Mode for anything with unclear blast radius, and encode "plan before big changes" as a rule in CLAUDE.md.

FAQ

Does Plan Mode write files?

No — it's read-only investigation that only presents a plan.

How do I switch to it?

Shift+Tab cycles modes, or start with `--permission-mode plan`.

Should I use it every time?

No — best for large, hard-to-scope changes; overkill for small fixes.

How is it different from hooks/permissions?

Plan Mode is a human-driven pause; hooks/permissions are deterministic, always-on blocks.

Find configs with safety built in →See School →See the All-Access plan →