Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Just use `claude update` if you already have it. Unfortunately, they removed Plan mode, when I could use Opus for planning and Sonnect for coding.

Though I will see how this pans out.



I am ended up not using this option anyway. I am using B-MAD agents for planning and it gets into a long-running planning stream, where it needs permission to execute steps. So you end up running the planning in the "accept edits" mode.

I use Opus to write the planning docs for 30 min, then use Sonnet to execute them for another 30 min.


> they removed Plan mode

This isn't true, you just need to use the usual shortcut twice: shift+tab


> Unfortunately, they removed Plan mode

If I hit shift-Tab twice I can still get to plan mode


I think they meant the 'Plan with Opus' model. shift+tab still works for me, the VS code extension allows you to plan still too, but the UI is _so_slow with updates.


They removed the /model option where you can select Opus to plan and Sonnet to execute. But you can still Shift + Tab to cycle between auto-accept and plan mode.


Oh thank God. parent comment made me think Plan mode was gone entirely by incorrectly stating that...Plan made is gone entirely...


You can use `/model opusplan` to get that behaviour back though if you do want Opus for planning and Sonnet for editing.


Thank you.


is Plan mode any different from telling Claude "this is what I'd like to do, please describe an implementation plan"?

that's generally my workflow and I have the results saved into a CLAUDE-X-plan.md. then review the plan and incrementally change it if the initial plan isn't right.


It also limits the tools available, reducing context usage and leaving more room actually to plan.


There's a bit of UI around it where you can accept the plan. I personally stopped using it and instead moved to a workflow where I simply ask it to write the plan in a file. It's much easier to edit and improve this way.


Yeah, I just have it generate PRDs/high-level plans, then break it down into cards in "Kanban.md" (a bunch of headers like "Backlog," "In-Progress", etc).

To be honest, Claude is not great about moving cards when it's done with a task, but this workflow is very helpful for getting it back on track if I need to exit a session for any reason.


i've experienced the same thing. usually i try to set up or have it set up a milestone/phase approach to an implementation with checklists (markdown style) but it's 50/50 if it marks them automatically upon completion.


I have this in my CLAUDE.md and it works better than 50/50. Still not 100% though:

### Development Process

All work must be done via TODO.md. If the file is empty, then we need to write our next todo list.

When TODO.md is populated:

1. Read the entire TODO.md file first 2. Work through tasks in the exact order listed 3. Reference specific TODO.md sections when reporting progress 4. Mark progress by checking off todos in the file 5. Never abbreviate, summarize, or reinterpret TODO.md tasks

A TODO file is done when every box has been checked off due to completion of the associated task.


> Unfortunately, they removed Plan mode

WTF. Terrible decision if true. I don't see that in the changelog though


No. Plan mode still works fine.

They just changed it so you can't set it to use Opus in planning mode... it uses Sonnet 4.5 for both.

Which makes sense Iif it really is a stronger and cheaper model.


It isn’t stronger for these sorts of reasoning tasks.


It is, according to the benchmarks. I'm just taking the materials they provided at face value.

If you have run your own benchmarks or have convincing anecdotes to the contrary, that would be an interesting contribution to the discussion.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: