ع
Learn Tracks Reference Guides Saved
feature

Plan mode

Ask Claude to think and propose a plan first — without touching a single file — so you approve the approach before any work happens.

Plan mode makes Claude lay out what it intends to do as a numbered plan and stop. Nothing changes until you read it and say go. In Claude Desktop you turn it on from the mode selector, or just ask for a plan in plain language in the chat ("plan it first, don't change anything yet"). It's the difference between 'just do it' and 'show me your plan, then do it' — perfect for anything bigger than a one-line fix.

In plan mode, Claude is read-only. It can look at your files, think the problem through, and write out a numbered plan — but it won’t change a single thing until you’ve read the plan and said go. The work hasn’t started; you’re approving the approach first. In Claude Desktop you turn this on from the mode selector, or just ask for it in the chat — “plan it first, don’t change anything yet.”

This is where the real savings hide. The cheapest possible place to catch a wrong turn is in a plan you can read in ten seconds — far cheaper than letting it run and then untangling the result. So read the plan like a skeptic. If step 3 would break existing users, say so, and Claude revises before anything happens. A plan is a draft to argue with, not a contract to rubber-stamp.

Use it for anything bigger than a one-line fix — and the bigger and less reversible the task, the more a plan earns its keep. It pairs naturally with checkpoints: plan mode keeps the wrong work from starting, checkpoints give you a clean way back if it does.

why it helps Catch a wrong approach in ten seconds of reading, instead of ten minutes of undoing.

examples
Ask for a plan before any changes
Add a dark-mode toggle to the settings page — plan it first, don't change anything yet.
Push back on the plan
Step 3 will break existing users. Revise the plan to migrate them safely.
tips & best practices
  • Use it for anything bigger than a one-line fix — the bigger the task, the more a plan saves you.
  • Read the plan like a skeptic: the cheapest place to catch a wrong approach is before it runs.
  • A plan is a draft to argue with, not a contract to rubber-stamp — tell Claude what to change.

Questions people ask

Does plan mode change any of my files?
No. In plan mode Claude is read-only — it can look at your files and write out a numbered plan, but it won't change a single thing until you've read the plan and said go.
When should I use plan mode?
Use it for anything bigger than a one-line fix. The bigger and less reversible the task, the more a plan earns its keep — catching a wrong approach in ten seconds of reading beats ten minutes of undoing it.
Can I change the plan before Claude runs it?
Yes — that's the point. A plan is a draft to argue with, not a contract to rubber-stamp. Tell Claude what to change ("step 3 will break existing users — revise it") and it reworks the plan before anything happens.
How is plan mode different from checkpoints?
Plan mode keeps the wrong work from *starting*; checkpoints give you a clean way *back* if it does. They pair naturally — plan to avoid the wrong turn, checkpoint to recover quickly when one slips through.
How do I turn plan mode on in Claude Desktop?
Pick it from the mode selector, or simply ask for a plan in plain language — "plan this first, don't change anything yet." Either way Claude writes out the approach and waits for your go before touching a thing.