What is plan mode?
Plan mode is a phase in which a coding agent reads the codebase and proposes a plan before it edits anything. Claude Code has it as the plan permission mode (Shift+Tab, /plan or --permission-mode plan), where edits stay blocked until you approve; Codex has /plan, and Cursor has Plan Mode.
- In Polish
- Tryb planowania
- First set up at
- Level 2, free guide
- Also searched as
- planning mode, plan first
$59.99 once for 12 months of access. Nothing renews on its own. 30-day refund on a first purchase.
Why it matters.
Reading a plan costs far less than reading a wrong diff. Plan mode makes the agent research and propose before it edits, so you catch the wrong approach while correcting it still means editing a document. Saved as plan.md next to the code, the accepted plan also gives review something to check the diff against.
One change, started two ways
The same request, with and without a plan between the prompt and the first edit.
- Text you or the model read and weigh
- A mode that runs
- What you can rely on
Straight to edits No gate
-
The request
Add a partial-refund endpoint
Nothing sits between the prompt and the first edit.
-
The agent
Edits the code
The guide’s example: a 900-line diff that edits the frozen
v1/package, bumps a dependency the platform team owns and tests only the happy path. -
Where you find out
In the diff, after the code exists
A five-minute read of a plan would have caught all three, but there was only the diff.
Plan first Edits blocked
-
The request
The same endpoint, in plan mode
Shift+Tabor/planin Claude Code,/planin Codex, Plan Mode in Cursor. -
The mode
The agent reads and proposes, and cannot edit
In Claude Code, edits stay blocked until you approve the plan.
-
You review
You correct a plan, not a diff
Changing course is still editing a document. A good plan names real files, symbols and proof commands.
-
What you can rely on
The accepted plan is committed as
plan.mdReview later checks the diff against that file.
How each tool does it.
Cursor, Claude Code and Codex each name this their own way. Each note carries the date it was checked.
Cursor
Plan Mode, which "creates detailed implementation plans before writing any code".
Cursor’s docs list four modes, Agent, Ask, Plan and Debug, and Shift+Tab cycles them: Ask is the read-only mode for questions, and Plan Mode is the one to use when the answer should become a plan (checked 2026-10-12).
Cursor docs, 2026-08-28
Claude Code
The plan permission mode: Shift+Tab, /plan or claude --permission-mode plan; edits stay blocked until you approve the plan.
Ctrl+G opens the proposed plan in your editor. Because plan mode blocks every edit, plan.md included, approve with "Yes, manually approve edits" and make plan.md the first approved edit.
Agent vs ask mode guide, Claude Code 2.1.283, 2026-09-26
Codex
/plan in the TUI switches to Plan mode; approval flags such as -a on-request are a separate control and do not make the agent plan first.
For a scripted planning run, keep the sandbox read-only with codex exec -s read-only. The beta permission-profile equivalent is -c default_permissions=":read-only"; do not combine the two.
Build-stage guide, 2026-10-12
Questions about plan mode.
When is plan mode worth the extra step?
For anything that touches more than one file, or when you could not yet write the acceptance criteria. For a task that is already specified, Agent mode is the right default.
Does Cursor have a plan mode?
Yes. Cursor documents Plan Mode, which "creates detailed implementation plans before writing any code" (docs read on 2026-08-28). It also has a read-only Ask mode: its docs list four modes, Agent, Ask, Plan and Debug (checked 2026-10-12).
How do I make plan mode the default in Claude Code?
Set "defaultMode": "plan" under permissions in .claude/settings.json. The VS Code extension ignores project settings for this, so set claudeCode.initialPermissionMode to plan in your VS Code user settings. It matters from v2.1.283 (both release channels on 2026-10-12), where interactive sessions start in auto mode and a question typed into a fresh session can turn into edits.
Does plan mode make the agent safe?
No. Plan mode controls when the agent may edit. It does not govern commands after approval, credentials, merge or deploy, so set the sandbox, approvals and branch protection separately. In Codex, -a on-request or -a never decides when it asks before running a command and does not make the agent plan first.
Keep reading.
The guides that go deeper, and the terms and comparisons next to this one.
In the docs
Related terms
Does this page answer your questions?
One tap, no sign-in.
What are you here for?
What is holding you back?
How does it read?
Thanks. If you left an email, Michał will reply.
Answering your questions?
One tap each. Close whenever you like.
no sign-in
Read the guides in the same words.
Open every guide with the Toolkit. Each term is defined once here, and the guides use it the same way.
$59.99 once for 12 months of access. Nothing renews on its own. 30-day refund on a first purchase.
Michał replies, not a bot. The address is used for this reply only.