What Claude does in plan mode
Plan mode is one of Claude Code’s permission modes. The docs describe it as telling 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. Edits stay blocked until you approve the plan, with one exception: in interactive terminal sessions with bypass permissions available, Claude is still told to plan, but an edit or command it attempts runs without a prompt.
Behind the scenes Claude can use the built-in Plan subagent, a read-only research agent meant for this mode. The plan itself is kept as a file, in ~/.claude/plans/ or the folder you set with plansDirectory.
How to enter it
- Shift+Tab in the terminal cycles the modes: Manual (
default), thenacceptEdits, thenplan. Auto mode, when available, comes last in the cycle, and from auto mode the first press goes back to Manual. The status bar shows⏸ plan mode on. /planat the start of a prompt puts that one prompt in plan mode.- At startup:
claude --permission-mode plan. - As your default: set
"defaultMode": "plan"underpermissionsin a settings file. - In VS Code: click the mode indicator at the bottom of the prompt box.
What happens when the plan is ready
Claude shows the plan and asks how to go on:
| Option | What follows |
|---|---|
| Yes, and use auto mode | Claude implements, with auto mode’s background checks instead of prompts. Without auto mode this reads “Yes, auto-accept edits”. |
| Yes, manually approve edits | Claude implements and asks before each edit. |
| No, keep planning | You stay in plan mode and give feedback. |
Before you pick, press Ctrl+G to open the plan in your editor and change it. That is often faster than describing the change in a prompt.
One trap: at the approval prompt, Shift+Tab approves the plan. To get out without approving, press Esc first.
The misunderstanding: “plan mode means Claude touches nothing”
Outside that bypass exception, plan mode blocks edits to your source, not all activity. Claude still runs shell commands to explore. Whether you are asked about each one depends on the session: when auto mode is available and the useAutoModeDuringPlan setting is on, which is the default, auto mode’s classifier reviews those commands instead of prompting you. If you want a session that cannot run anything outside a fixed list, plan mode is not that tool; permission rules and dontAsk mode are. More on the modes in what auto mode is.
When it helps, and when to skip it
Plan mode earns its turn when a wrong direction is expensive:
- Exploring a codebase before changing it, the use the permission docs name for it.
- Larger or risky changes, where you want to agree on the approach first. The costs guide recommends plan mode for complex tasks because it prevents expensive rework when the initial direction is wrong.
- Work you hand to others: in an agent team, a teammate started while the lead is in plan mode plans first and only implements after its plan is approved.
For a one-line fix or a change you can describe exactly, planning adds a round trip without much gain. A specific prompt already does most of the work.
What this means for a team
A plan is the cheapest moment to catch a wrong assumption, and it is readable by people who were not in the session. Pasting the plan into the pull request or the issue lets a reviewer see what was intended before reading the diff. But a plan is only as good as what Claude knew when writing it. It reads the repo and CLAUDE.md, not the decision someone made in a call last week. See also how subagents keep exploration out of your session and how to use Claude Code well.
Where Bombos fits
A plan is built from what Claude can see. Bombos is a plugin that gives Claude Code and the team’s other AI tools one shared memory with the context a plan usually misses: team decisions, rules learned from earlier corrections, and what is in mail, documents and other repos, each traceable to its source. One developer can try it on their own agents first.
Related questions
Is it called planning mode or plan mode?
The official name is plan mode. The status bar shows ⏸ plan mode on, and the setting value is plan.
Can I edit the plan before Claude starts?
Yes. Press Ctrl+G to open the proposed plan in your text editor and change it directly before Claude proceeds.
How do I leave plan mode without approving?
With no approval prompt open, press Shift+Tab to move on in the cycle. At the approval prompt, press Esc first, because Shift+Tab there approves the plan.
Can I start every session in plan mode?
Yes. Set permissions.defaultMode to "plan" in your settings file, or start with claude --permission-mode plan. In VS Code, click the mode indicator under the prompt box.
Does plan mode cost extra?
Planning itself uses tokens like any turn. The costs guide recommends it for complex tasks because it prevents expensive rework when the first direction is wrong.
