Enter Plan Mode for the right problems
Use planning for unclear requirements, architecture changes, migrations, or work with a wide blast radius. A one-path typo fix or read-only investigation usually does not need the ceremony.
Enter with /plan, add the task description on the same command when useful, or cycle modes with Shift+Tab. Ask the agent to identify unknowns and inspect the repository before committing to a design.
/plan
/plan Migrate authentication to rotating JWTs without changing the public API.Review the plan as an artifact
The preview remains visible even under auto or always-approve. Comment on a selected line or range, request changes, and approve only when the sequence and proof are credible.
Reopen a saved preview with /view-plan. The review should expose affected files, data migration, compatibility risk, tests, observability, and rollback where those concerns apply.
- a: approve and build.
- s: request changes.
- c: comment on the selected line or range.
- q: leave Plan Mode without executing.
/view-planUnderstand what the gate does not stop
Before approval, only the session plan file may be edited through edit tools. Reads, bash, and MCP still follow the active permission mode, and shell redirection can write files. Plan Mode is therefore not a security sandbox.
Parent Plan Mode also does not edit-gate a subagent, although the child inherits the permission mode. For sensitive repositories, combine planning with narrow permissions, sandboxing, and explicit instructions against mutation.
- Inspect git status before and after planning.
- Do not grant broad shell access merely because edits are gated.
- Re-check the diff after approval.