How Do You Make Claude Code Plan Before It Edits?
Use plan mode. Press Shift+Tab until the status bar shows ⏸ plan mode on, start with claude --permission-mode plan, or put /plan in front of one prompt. Claude reads files, runs commands to explore and writes a plan, and its edits stay blocked until you approve.
/plan [describe the change, naming the folder and the symptom or goal] The plan must list: - each file you'll change, and what changes in it - the order of the changes, and where I could safely stop - how you'll verify it: the exact command, and what passing looks like - anything you assumed because you couldn't confirm it from the code - what you're deliberately leaving out If two approaches are reasonable, show both and recommend one. Ask me first if a decision isn't yours to make.
- 1Enter plan mode
- 2Claude reads and writes a plan
- 3Edit it with Ctrl+G
- 4Pick an approval option
Try it now
- 1Paste the prompt above with a real multi-file task. Run
git statusfirst so you know the starting point. - 2When the plan appears, press
Ctrl+Gto open it in your text editor and change it directly. - 3If it's wrong, choose No, keep planning and say what to change. The first few times, approve with Yes, manually approve edits so you see each edit.
- 4You'll know it worked if
git statusshows no new source changes until after you approve.
Use it when
Changes that span several files, unfamiliar code, or any task with two reasonable approaches where you care which one gets built. It also suits a task you plan to step away from, since the plan may be the only part you review closely before it runs.
Skip it when
A typo, a rename or a one-file fix you can describe in a sentence. The plan adds a round of tokens and reading, and tells you nothing new. It also doesn't replace checking the result: a plan says what Claude intends, so you still need tests or a review afterward.
Why it works
Plan mode is a permission mode, so apart from one exception covered below, Claude Code blocks the edits itself instead of relying on the model to hold back. When the plan is ready, you choose Yes, and use auto mode, Yes, manually approve edits or No, keep planning. Approving exits plan mode and switches to the mode that option describes, so the same click decides how much of the implementation you'll review. Rule of thumb, not a vendor figure: a wrong direction costs a sentence to fix at this stage, and a review and a revert once the files have changed.
Example
Say you run /plan add per-key rate limiting to the public API in src/api/. Suppose the plan adds a check to each route handler, and your team wants this in the shared middleware. Choose No, keep planning and write put this in the middleware in src/api/middleware, not in each route. Claude revises the plan, and no source file has changed. That redirect is the whole point: you're correcting a paragraph, and no diff exists yet.
Going further
Plan mode has one hole. In interactive terminal sessions with bypass permissions available, the docs say Claude Code doesn't enforce its blocks: Claude is still told not to edit, but an edit or command it attempts runs without prompting. Planning also isn't limited to read-only commands. When auto mode is available, the classifier reviews shell commands instead of prompting you, through useAutoModeDuringPlan, which is on by default. Turn it off to be asked about anything outside the read-only set. To plan by default in a repo, set permissions.defaultMode to plan in .claude/settings.json. Plan files live in ~/.claude/plans/, or wherever plansDirectory points.
Common mistakes
- Choosing Yes, and use auto mode without noticing you've also stopped reviewing edits. Approval switches the session to that mode.
- Expecting plan mode to stick. After you approve, the session leaves it, so press
Shift+Tabor start your next prompt with/planto plan again. - Approving a plan with no verification step. Claude then has no check to run, and stops when the work looks done.
- Setting plan mode in the project's settings and expecting VS Code to follow it. The docs say sessions started by the extension don't read project settings for the starting mode, so set
claudeCode.initialPermissionModein your user settings.
Sources
- Choose a permission mode, Claude Code docs
- Common workflows, Claude Code docs
- Commands, Claude Code docs
Checked 6 November 2026. Products change often, so confirm details with the vendor.