← back to the archiveCover illustration for “Plan mode: let the coding agent think before it edits”
TERM7mo ago·Published · Updated ·by Andy Padia

Plan mode: let the coding agent think before it edits

In short: Plan mode makes a coding agent research the codebase and propose a plan before it edits any file, so you can correct the approach while it is cheap.

Plan mode is a coding-agent setting where the agent researches the codebase and proposes a plan, and makes no edits until you approve it. In Claude Code you start a session with claude --permission-mode plan or press Shift+Tab until the status bar shows plan mode, according to the common workflows documentation read in November 2026. It is a cheap way to catch a wrong approach before it touches code.

Plan mode in plain words

It is asking the builder for a drawing before they start knocking down walls.

How it works

Claude Code treats plan mode as a permission mode. Per the permission modes documentation, Claude reads files and runs shell commands to explore, then writes a plan, and it does not edit your source until you approve. You can also prefix a single prompt with /plan.

When the plan is ready you choose between approving with auto mode, approving with manual review of each edit, or continuing to plan. Ctrl+G opens the proposed plan in your text editor, so you can change it before the agent proceeds.

Example

As an illustration:

[plan mode] Add rate limiting to the public API.
Plan: 1) add middleware in api/middleware/rateLimit.ts using the existing
  Redis client, 2) apply to /v1/* routes only, 3) return 429 with Retry-After,
  4) add tests for burst and reset, 5) document limits in docs/api.md.
  Question: should authenticated users get higher limits?

The question at the end is the point: you answer it before any code exists.

Where you'll meet it

  • Claude Code's plan mode
  • Similar planning or "ask" modes in other coding agents and IDEs
  • Spec-driven workflows that write plans to files
  • Larger refactors, migrations and unfamiliar codebases

What it changes for you

For developers, my view is that planning first pays for itself on anything bigger than a small fix. For tech leads, saved plans become reviewable design notes. For teams new to agents, plan mode is a safe way to learn how the agent thinks before giving it write access.

Plan mode vs spec-driven development

Plan mode is a session setting for one task. Spec-driven development is a whole workflow where written specs and plans become versioned artefacts that drive the build.

Common mistake

My view: approving the plan without reading the assumptions. A wrong assumption stated plainly in the plan becomes a wrong change once nobody challenges it.

Spec-driven development · Permission modes · Claude Code · Agentic coding

Read the assumptions in the plan before you approve it, because an unchallenged assumption becomes a wrong change.

#field-guide#claude-code#coding-agents#planning#workflow

Sources

  1. code.claude.com/docs/en/common-workflows
  2. code.claude.com/docs/en/permission-modes
← older drop
Foundation model: one big model, adapted to many tasks
newer drop →
LLMOps: running LLM applications in production

related drops

explore all 557 drops →
← back to the archiveday 175