Plan Mode & Interrupting

What Plan Mode is

Normally, Claude starts working as soon as you send a task. In Plan Mode it does something different: it explores your project, thinks the task through, and presents a plan — which files it will touch and what it will do — then waits. Nothing is edited until you approve. You're reviewing the blueprint instead of the finished wall.

How to turn it on

Press Shift+Tab to cycle input modes and watch the small mode indicator by the prompt — one of the stops is Plan Mode. Cycle again to leave it. You can also simply write "make a plan first, don't change anything yet" in the task itself; the keyboard mode is the same idea with guardrails.

When to use it — the 3+ file rule

  • Use Plan Mode for any task likely to touch three or more files, anything structural (new sections, refactors, renames), and always when starting a brand-new project.
  • Skip it for small, single-file tweaks — "fix this typo" doesn't need a blueprint.

The logic is economics: a wrong plan costs you thirty seconds to reject. Wrong code costs minutes to spot, more to unwind, and the session's context is polluted with the failed attempt. Catch wrong directions at the cheapest possible moment.

How to review a plan like a pro

You're not grading prose — you're checking four things:

  1. Scope: does it touch the files you expected, and only those? A plan that "also improves" things you didn't ask about is the classic AI failure mode — say no to the extras.
  2. Understanding: does the first paragraph restate your goal correctly? If it misunderstood the task, everything after is decoration.
  3. Verification: does the plan say how it will prove the change works (build passes, page renders, test green)? If not, add it.
  4. Questions: a good plan often asks you to decide something. Answer properly — those decisions are the actual steering wheel.

If the plan is wrong, say why and ask for a revision. Rejecting a plan costs nothing; you're teaching Claude what you actually meant while the price is still zero.

Esc — interrupt early, interrupt often

Outside Plan Mode (and inside it), Esc stops Claude mid-action. The moment you see it head the wrong way — opening files that can't be relevant, "improving" something you didn't ask about — press it. Two things beginners should know:

  • Interrupting is normal. Professionals stop the agent constantly. Letting a wrong idea run to completion out of politeness is the expensive choice.
  • Stopping is not undoing. Edits made before you pressed Esc are still on disk — check the Source Control diff, then ask Claude to revert, or use /rewind (next chapter).

Real-world example — this very track. The Learn Claude Code section you're reading was built in Plan Mode first: the chapter list, URLs and file structure were proposed and approved as a plan before a single page was written. The plan review took a minute; it shaped seventeen chapters.

Up next: why long sessions make Claude slower, dumber and pricier — and the small set of habits (/clear, /compact, /rewind) that keep every session sharp.

FAQ

Frequently Asked Questions

What is Plan Mode in Claude Code?
A mode where Claude explores your project and presents a plan — which files it will touch and what it will do — and waits for your approval before editing anything. You review the blueprint instead of the finished wall.
How do I turn Plan Mode on and off?
Press Shift+Tab to cycle input modes; one of the stops is Plan Mode (watch the indicator by the prompt). Cycle again to leave it.
When should I use Plan Mode?
The rule of thumb: any task likely to touch three or more files, anything structural (refactors, new sections, renames), and always when starting a new project. Skip it for one-file tweaks.
Does pressing Esc undo what Claude already did?
No — Esc stops the current action, but edits made before you pressed it are still on disk. Check the Source Control diff, then ask Claude to revert or use /rewind.