Before and after

Claude Code plan mode: one task, with and without a plan

Updated November 17, 20268 min read

Claude Code plan mode makes Claude read your project and write a plan before it changes a single file. Turn it on with Shift+Tab, the /plan command, or claude --permission-mode plan. Below, the same request is run twice, once straight away and once in plan mode, so you can see what the plan step actually changes. Then come the keys, a checklist for judging a plan, and the cases where planning is a waste of time.

The test task: a dark mode switch

Running several sessions at once? A finished plan sits silently until you look at it. VibeCodingDeck gives each Claude Code pane a status light and a sound when an agent is waiting, so a plan never waits long for your approval.

The example below is a made-up but typical case. A small website has a header, a settings page and a few pages of content. The owner wants a switch in the header that turns the site dark, and wants the choice remembered next time. The request is the same in both runs:

add a dark mode switch to the header. remember the choice when the page reloads.

It sounds like a one-file job. In most real projects it is not: colours live in several places, some pages may hard-code a white background, and remembering the choice means saving it somewhere. That hidden size is exactly where plan mode earns its keep.

Run 1: straight to code, no plan

  1. Claude reads the header file, adds a button and writes a small script that adds a dark class to the page.
  2. It writes dark colours into the main stylesheet and saves the choice in the browser.
  3. It reports the task as done. The header looks right.
  4. You click around. The settings page is still bright white, because it uses its own colours. A chart on one page is now unreadable, dark text on a dark background.
  5. You ask for fixes. Claude patches the settings page, then the chart. Each fix is a new round, and each round re-reads the growing conversation.
  6. On reload, the page flashes white for a moment before turning dark, because the choice is applied after the page draws. Another fix.

Nothing here is a disaster. Each step was reasonable on its own. The problem is that you found the real shape of the job one surprise at a time, after code was already written, and each correction cost more usage and attention than the last.

Run 2: the same request in plan mode

  1. You press Shift+Tab until the bar says ⏸ plan mode on, then send the same request.
  2. Claude searches the project for colour values, finds the main stylesheet, the separate settings page styles and the chart settings.
  3. It notices that a saved choice applied after load causes a flash, and plans to apply it before the page draws.
  4. It writes the plan and asks how to proceed. No file has changed yet.
  5. You read it, ask it to leave the chart for a second task, and approve.

The plan Claude shows looks something like this (shortened):

Plan: dark mode switch

1. Move colours into CSS variables in styles/main.css
2. Add a dark set of the same variables under .dark
3. Replace hard-coded colours in settings/settings.css with the variables
4. Add a toggle button to components/Header
5. Save the choice in localStorage and apply it in a small script
   in the page head, before the page draws (prevents a white flash)
6. Out of scope: chart colours (separate task)

Test: toggle on every page, reload, check settings page and header

The build that follows is calmer because the surprises were found while they were still cheap: in a text file, not in your code.

What the plan changed, side by side

MomentWithout plan modeWith plan mode
First replyCode changesA written plan, no files touched
Hidden work (settings page, flash)Found by you, after the factFound by Claude, before coding
ScopeGrew with each fixAgreed up front, chart moved to a later task
Your roleTester and bug reporterReviewer of one document
Undoing a wrong directionRewind or fix forwardSay no to the plan

Anthropic's own cost guide makes the same point: plan mode for complex tasks prevents expensive rework when the first direction is wrong. Exploring costs some usage, but rewriting the wrong files costs more. Our Claude Code pricing page has more on stretching your plan.

How to use plan mode in Claude Code: four ways in

# 1. Keyboard, during a session
Shift+Tab   (press until the bar shows: ⏸ plan mode on)

# 2. Slash command, for one task
/plan fix the login bug

# 3. Start a whole session in plan mode
claude --permission-mode plan

# 4. Make plan mode the default for a project (.claude/settings.json)
{
  "permissions": {
    "defaultMode": "plan"
  }
}

/plan on its own just switches modes. Add a description after it and Claude starts planning that task straight away. The project default in option 4 applies to terminal sessions. The VS Code extension does not read that project setting, so there you set claudeCode.initialPermissionMode to plan in your VS Code user settings instead.

While planning, Claude can read files and run commands to explore. If auto mode is available on your plan, a background safety check reviews those commands instead of asking you each time. If it is not, commands outside a built-in read-only set ask for approval.

Claude Code plan mode shortcut keys at the approval prompt

  • Yes, and use auto mode: approve and let Claude build without asking about each edit. It reads Yes, auto-accept edits if auto mode is not available to you.
  • Yes, manually approve edits: approve, but you confirm every edit. Best while you are learning.
  • No, keep planning: stay in plan mode and type what to change.
  • `Ctrl+G`: open the plan in your text editor, change it, save, and Claude works from your version.
  • `Esc`, then `Shift+Tab`: leave plan mode without approving. Careful: pressing Shift+Tab while the approval prompt is open approves the plan.

Behind the scenes, Claude can hand research to its built-in Plan subagent, a read-only helper that gathers context without filling your main chat. You do not need to set anything up for that. More on helpers in our subagents guide.

Plan mode vs auto accept edits and the other modes

ModeStatus barWhat Claude does without asking
Manual (default)⏸ manual mode onReads files only
Accept edits (acceptEdits)⏵⏵ accept edits onEdits files and runs common file commands like mkdir, mv and cp in your folder
Plan (plan)⏸ plan mode onReads and explores, edits nothing until you approve
Auto (auto)⏵⏵ auto mode onMost actions, with background safety checks
Bypass (bypassPermissions)⏵⏵ bypass permissions onEverything

Plan mode and accept edits answer different questions. Plan mode is about when Claude may change files: not until you agree on the approach. Accept edits is about how often it asks: once you trust the direction, it stops asking about each edit. They work well together. Plan first, then approve with auto-accept so the build runs without interruptions.

Shift+Tab cycles manual, then accept edits, then plan, followed by any optional modes you have turned on. Source: Anthropic's permission modes page, as of November 2026.

Checklist for a plan worth approving

  • It names the files it will change, and none of them surprise you.
  • It says what it will delete or rename, if anything.
  • It lists anything it is deliberately leaving out.
  • It reuses code you already have instead of adding a new library you did not ask for.
  • It explains how the finished work will be checked: a test, a build, or steps you can click through.
  • It covers existing data or users, for example how saved settings survive the change.
  • It is small enough to review. If not, ask Claude to split it into stages and approve one stage at a time.
  • You could explain it to someone else in a sentence or two.

If one of these is missing, do not approve yet. Ask, for example, what could go wrong with this plan? or how will you test step 3?. Questions at this stage cost very little.

Claude Code plan mode tips from daily use

  • Start from a clean slate with /clear, so an old conversation does not steer the plan.
  • Put the goal, the limits and the meaning of "done" in the request itself.
  • Ask for options when you are unsure: give me two approaches with the trade-offs.
  • For a fuzzy idea, ask Claude to interview you and write a spec file first, then plan from the spec in a fresh session.
  • After approving, ask Claude to run the test or build and show you the output before it calls the job finished.
  • When several agents plan in parallel, give each one its own copy of the project. Our worktrees guide explains how.
/plan add password reset. reuse the email helper in src/lib/email.ts, no new libraries. done = I can request a link, set a new password and log in. list every file you will touch.

/plan the checkout page is slow. find out why before changing anything and give me two options.

When to skip plan mode

Planning has a cost: Claude spends time and usage exploring before it writes anything. For small, obvious jobs that cost buys you nothing. Good times to skip:

  • Fixing a typo, renaming a variable, or changing one line of text.
  • A change you would describe as a single, obvious edit to one file.
  • Quick questions about the code, where nothing will be edited anyway.
  • Throwaway experiments in a copy of the project that you plan to delete.

On the other side, always plan for anything touching sign-in, payments, deleting data, database structure or many files at once. If you are new to this, our beginner Claude Code course treats plan mode as lesson 4 for that reason.

Plan mode, quickly answered

What is the shortcut for plan mode in Claude Code?

+

Press Shift+Tab until the status bar shows ⏸ plan mode on. You can also type /plan, or start with claude --permission-mode plan.

Can Claude edit files while in plan mode?

+

No. It can read and explore, but it does not edit your source files until you approve the plan.

How do I make Claude Code always start in plan mode?

+

Add "defaultMode": "plan" under permissions in your project's .claude/settings.json. In VS Code, set claudeCode.initialPermissionMode to plan instead.

How do I leave plan mode without approving the plan?

+

Press Esc at the approval prompt first, then Shift+Tab to change mode. Pressing Shift+Tab while the prompt is open approves the plan.

Sources

Run up to 12 AI coding agents in one window.

Claude Code, Codex, Gemini, Grok and more, side by side. Windows and Mac. From $29 a month.

Get started

Keep reading