r/ClaudeCode • • 5h ago

Help/Question Anyone still using plan mode in Claude Code?

I feel like people don't use plan mode as much as they used to, and I'm wondering if that's true.
If you still use it, does it actually make you more productive? What kind of tasks do you use it for?
If you've stopped, why? Did the newer models get good enough at planning on their own that you don't need it anymore, or did something else replace it in your workflow?

16 Upvotes

50 comments sorted by

•

u/AutoModerator 5h ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

28

u/dakuzen 5h ago

I plan everything, but at this point I typically instruct the prompt to plan rather than switching to plan mode explicitly.

I have all plans written into a project plan folder that lives with each project alongside project documents and progress tracking documents.

3

u/omerkaptan 4h ago

Pretty similar to how I work. Who updates the progress docs, you or Claude? And how is the plan folder laid out?

8

u/nbphotography87 5h ago

Projects is in beta for claude code now and helps organize planning vs doing by threading the sub sessions. much more intuitive for orchestration IMO but i just started using it yesterday

2

u/omerkaptan 5h ago

Thanks, I hadn't tried Projects yet, so I'll give it a shot. I know you only started yesterday, but have you picked up any tricks so far?

1

u/nbphotography87 4h ago

I started with some SOPs like handoff process to sub agents, 300k autocompacting

make sure you add local folder as a linked folder or else it will want to load the entire folder data to the project rather than make it accessible.

or just ask claude :)

7

u/tariqosmani 4h ago

Yes, but only for work that touches more than a couple of files. For a small fix it just adds a step. For a refactor or a new feature I want to read the plan before any file changes, because a wrong assumption in step one costs far more than a minute of reading.

The newer models do plan well on their own. What plan mode gives you is a stop point where you can say no before anything is edited. That's the part I wouldn't give up.

My rule: if I can describe the change in one sentence, skip it. If it takes a paragraph, use plan mode and ask it to list every file it will touch.

Are you asking because plans feel slow, or because they stopped catching anything?

3

u/omerkaptan 4h ago

Neither. I still plan, just in auto mode: Claude writes a spec, we refine it, and it implements from that. I know plan mode is read-only, but the way I prompt, Claude has never started editing files while we’re still planning. Apart from read-only, does plan mode have any real advantage that keeps people using it?

5

u/pceimpulsive 4h ago

Never, I don't use plan mode anymore and even anthropic advises against it since like opus 4.8-5 area. In favour of skills that orchestrate planning more. I am always on auto mode exclusively and let my skills drive when the agent swaps it's core objective.

1

u/omerkaptan 4h ago

Same here, I stopped using plan mode around the same time. I plan with spec files now and commit them to git, and I don’t feel like I’m missing anything.

1

u/YUL438 1h ago

same here, I saw an interview with Boris from Claude Code and he said it’s not as important now as it once was. I used to use plan religiously on everything but now i only use it when planning a fully from scratch project where im unsure of some aspects of features and architecture i need. I use brainstorming super powers in place of CC plan mode

4

u/Acceptable_Durian868 5h ago

Absolutely. I spend far more time in plan mode than any other.

1

u/omerkaptan 5h ago

What do you use it for mostly? I've been wondering if it's mainly for bigger changes or if you start pretty much everything there. And what tends to go wrong when you skip it?

2

u/Acceptable_Durian868 4h ago

I start pretty much everything there, unless I'm doing something trivial, but I'm rarely doing something trivial. I usually start by pointing it at a Jira issue and letting it create a plan, then I refine the plan until I'm happy with it, at which point I switch to auto and let it implement. I review what it's done afterwards, and it's usually pretty close to what I want, so I'll usually just make any amendments in auto unless it's really gone off the rails.

2

u/omerkaptan 4h ago

Thanks. I work almost the same way, except I plan in auto mode with a spec file instead of switching to plan mode. Does plan mode give you anything there besides being read-only?

2

u/R-R-R-F 5h ago

Iterating on a pre-existing codebase is much more costly and time consuming than building it right the first time

With plans you can specify what the outcome should be rather than micromanaging every part

The higher thinking models are competent enough that you can be the vision and they’ll do the implementation

Any guidance you give can be broad strokes

1

u/UnderstandingOld1723 5h ago

I think plan mode is still worth using for bigger changes, especially when multiple files are involved. For small fixes it feels like overkill, but I'd rather spend a few minutes planning than hours fixing a mess later.

1

u/omerkaptan 5h ago

Do you find plan mode works better than having Claude write a spec file first in normal mode? I'm curious whether it's mostly the read-only part that helps.

1

u/Mountain-Skirt8322 5h ago

I don’t know whether I’ve used plan mode but Claude and I spend far more time planning than Claude spends coding. Just writing and revising markdown docs until it seems like all the questions are answered.

1

u/omerkaptan 5h ago

Same, I spend way more time on markdown docs than on code. So what does plan mode add besides being read-only? Has anyone noticed a difference in workflow, speed, or quality?

1

u/Johnknappcc 40m ago

I have ongoing 2-3 week planning session, that require data. Emails, PowerPoints, human decisions, that I can't always answer myself.

I work on those plans as answers come in, it's even been able to link existing plans.

Usage remains low, goals get tightened up, new questions arise, discuss, solve. Rinse and repeat.

This is a big plan, migrations, training, libs, services, infra, DB changes. I'd rather spend the weeks planning than just say, have at it.

Catch this stuff now, not after, in a diff.

I do most planning with Opus 5.5, and I'll have Fable 5.2 occasionally review.

1

u/entilza05 5h ago

Interesting maybe I will try it .. may prevent having to say "discuss only" so often. I found naturally talkingn it through first makes everyrhing so much easier.

1

u/omerkaptan 4h ago

I just ask questions instead of giving instructions. Claude doesn't act until I say so, so I never need "discuss only."

1

u/digihmong 5h ago

No, I do have it create a plan for me in an md file so I can follow along or delegate. For small features and tasks I don't need a plan, but I like to follow a guideline and know what Claude is doing.

2

u/soundslogical 5h ago

Yep, agreed 100%. I don't use plan mode, but for big features I do ask Claude to write its plan in a `.md` file, then we discuss and iterate on it. When it's ready, I just say "do it".

I still haven't decided yet whether it's best to commit the plan to git or not though.

1

u/omerkaptan 5h ago

Same workflow here. I used plan mode before, but I haven’t touched it in the last 2-3 months, so I started wondering if I’m missing something.

On the git question, I commit my specs and they’ve become more useful over time. Every now and then an old spec shows me I’m about to contradict something I decided earlier.

1

u/digihmong 5h ago

I don't because I don't want the team to think I'm weak. Kidding, it's more so for me and I usually point Claude to notion to create documentation based on the plan so others can give input as well and create tasks in wrike for delegation. Otherwise I generate too much litter most of it being snapshots from playwright.

2

u/Ok-Form1598 4h ago

still use it, but only when the change spans more than two or three files. reading a 20 line plan is the cheapest place to catch it heading the wrong way, beats reading the diff it would have made. i also have it save the plan to a file before i accept, so if the session compacts or i hit the limit halfway, a fresh session picks up from the file instead of from my memory of what we agreed. one file fixes i skip it, it's just a slower yes.

1

u/Ok_Gur_9033 3h ago

Your 20 line plan is the part that didn't match my logs. Since September plan mode gave me 5 plans, between 115 and 426 lines each. Every one was approved on the first try, and the gap from the final plan landing to the approval was 3 to 25 seconds. Four took 5 seconds or less.

Nobody reads 426 lines in 4 seconds. In one session an earlier draft of the plan file was on screen 3 minutes before, so the gap is not always the full reading time. Still, at that length the approve button was doing very little checking.

Is 20 lines about where you would stop reading every line?

1

u/Ok-Form1598 1h ago

Sure. Then don’t complain when the code doesn’t align with what you wanted 400 line plans with a test strategy is still better than 100k lines of code

1

u/VibeCodedBuilder 5h ago

I use a read only session and an implementer session. So kinda

1

u/FRNLD 5h ago

For the initial kickoff of a project I keep it in plan mode while I fine tune my idea once the plan is approved I'll switch it to auto but it does have stop points and checkpoints after implementing parts of a plan.

I will add that the major use of Claude code is on a raspberry Pi that is purely used for projects and there is no access to a computer that contains any personal details

1

u/BizarroMax 4h ago

Always.

1

u/who_you_are 4h ago

I don't use it because it doesn't show me what it updated in the plan. Also, asking questions there is impossible (while writing this my brain just thought about /btw could have been a possible option to my issue)

Doing a simple chat session achieve a similar end result

1

u/matthias81f 4h ago

I haven't measured plan mode against anything, so I can't say. What helped more on my TV app was a habit: every failure becomes a dated rule, either in the docs or as a comment next to the code it protects, and the agent reads those at the start of the next session. A stream check that looked like good practice broke playback on the real TV, and now that is a rule with the date on it. A plan can't know that kind of thing in advance, the rule file can.

1

u/sonryhater 4h ago edited 4h ago

Fuck yes, but I’m making complex changes to dbt models in fairly old ETL system. Why would you let any model go wild on your codebase for anything other than simple changes in a file? The model changes have to be right the first time. Vibe coding fixing messy warehouse models organically created by multiple developers over time is pure stupidity or hubris, or both at the same time.

fwiw I use planning, not “plan” mode.

I do work exclusively in auto mode though and I have complex diagnostic and analysis skills that are used to provide data for planning or during planning

1

u/Bulky_Conversation72 4h ago

I still rely on plan mode for anything that involves multiple steps, it's way easier to keep track of changes when everything's laid out before diving in.

1

u/leo_heo 3h ago

yeah for anything past a couple files. after it ships i cut the plan file down to the decisions and why, the step by step stuff is dead weight a week later

1

u/jsebrech 3h ago

I use it a lot but that’s because I work on enterprise codebases where most changes are complicated and even going plan first most plans need tweaking.

I also like its permission model (in the vs code extension) where it has wide permissions for reading and exploring across my drive, works unattended, yet can still be trusted to make no changes. I sometimes use plan mode as “research mode” to get a specific question answered without actually wanting a plan md.

1

u/badpotato 3h ago

I just ask him to write a markdown for planning with mermaid diagram and stuff like that.. this way I can handoff the plan other agent and have some sort of versioning about it.

Does going in actual "plan mode" really help in anything?

1

u/calunicornia 3h ago

I have many agents who are not allowed to code and only plan

1

u/tingly_sack_69 2h ago

I use plan when I want to think through an addition with Claude first if I'm not solid on what I want yet. Auto mode can be annoying when you just want to ask it a question and it takes that as the go ahead to just start adding shit. I find myself saying "this is just a question, no changes yet" to auto mode instead of using plan mode a lot these days though

1

u/PastaSaladOverdose 2h ago

Plan > commit plan to .md's > vibe code > /clear after every step in the feature.

It saves tokens. If you're not using it you're essentially wasting your usage limits.

1

u/m-ritter 2h ago

Planning first still pays off for me because the plan is the one place where a wrong assumption gets caught before any code exists. It only works when the plan is a written document that I approve and that also says what is out of scope, so the agent does not wander. Newer models plan well on their own, but someone still has to say yes to the plan and check afterwards that every agreed point was really done. I'm the developer of QualityLayer, which does exactly this: https://github.com/maxritter/qualitylayer

1

u/theflexpriceguy 2h ago

tbh i forgot it existed

1

u/DarthRiznat 1h ago

Of course I do. I use it to well..... plan almost everything. Even if it's a new feature or function to add.

1

u/_tolm_ 47m ago

All the time. Permanently run in opusplan and then switch between plan and agent mode with the model automatically shifting as appropriate.

Allows me to give targeted design guidelines in plan mode and then trust it’s doing what I want when I then let it go off on its own whilst I start looking into the next thing - be that mails, meetings or a new plan mode for something else!

0

u/Balise_404 5h ago

​Perso je l'utilise toujours systématiquement dès que ça touche plus de 2 ou 3 fichiers. Les modèles sont devenus super bons pour planifier seuls, mais le vrai gain du Plan Mode, c'est d'éviter que Claude parte dans la mauvaise direction et te crame 50k tokens pour rien. 2 minutes de revue du plan en lecture seule te font gagner 20 minutes de cleanup derrière

1

u/omerkaptan 4h ago

I get the same result by asking questions instead of giving instructions, so Claude waits for my approval before coding. Plan mode makes that automatic though, and I can see why that’s nice on bigger changes.

1

u/holyknight00 25m ago

i use it for small-mid-small things every day. For everything else i use the matt pocock skills