Bring back "opusplan", why did you remove it in v2.0.0?
Resolved 💬 40 comments Opened Sep 29, 2025 by PaulRBerg Closed Feb 18, 2026
💡 Likely answer: A maintainer (dicksontsai, collaborator)
responded on this thread — see the highlighted reply below.
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
opusplan was an option for /model that was available in v1.0.x, which enabled us to use Opus for planning and Sonnet for implementation. The CLI was automatically switching between Opus and Sonnet without us having to manually toggle between them after the planning session is done.
Why has it been removed in v2.0.0?
<img width="700" src="https://github.com/user-attachments/assets/ace0d3f3-ffa5-477b-92dd-1060372ee733" />
Proposed Solution
Bring opusplan back!
Priority
High - Significant impact on productivity
Feature Category
Configuration and settings
40 Comments
I rely heavily on Opus Plan mode myself. I'm curious if this change was made because Anthropic believes Sonnet 4.5 is a better planner than Opus 4.1?
if I were to guess, it wasn't an intentional change. Prolly just a vibe-coded removal
this is a huge downgrade in terms of UX, guys, PLEASE bring
opusplanback!FWIW you can still still set this in your
~/.claude/settings.json:And it still works normally with Opus for plan and Sonnet for act... I'm guessing it was erroneously removed as a UI option
I'm all up for innovation at the speed of thought, but if it's not tested... Please please please Claude team, do not rush. You are already better than OpenAI Codex, don't make me switch because you drop the ball and rush releases.
Thank you for the fix @wpfleger96
Even when using
/model opusplanor setting"model": "opusplan"in mysettings.json, when I ask it what model it's using it always appears to at least think it's using Opus. The model on my statusline is what I expected it to use (Sonnet 4.5).<img width="758" height="481" alt="Image" src="https://github.com/user-attachments/assets/aba3a585-72f8-4c33-bfa1-dc62283286b2" />
I set
opusplaninsettings.json, and this is what I see when I runclaude:Very confusing and I'm not sure now if @wpfleger96's fix actually works.
<img width="500" src="https://github.com/user-attachments/assets/289a8443-cdb2-4872-9b38-0aa27720a125" />
@PaulRBerg I'm reasonably sure it doesn't; I asked mine a few times when swapping through the various modes what model it was using and it stuck with Opus every time regardless of whether I was using
Planor not.then this is a bug and it should be fixed ASAP
I will go back to v1.0.128 in the meantime
According to Anthropic's own benchmarks, Sonnet 4.5 is currently a better model than Opus 4.1 across the board. This might be a case that it's removed as an option until a better version of Opus is released.
It seems like the UI is more buggy than I initially noticed... I may have an idea what's going on here by inspecting the debug logs from my custom statusline script
First, I think setting
opusplanin~/.claude/settings.jsonis "working" in that it uses Opus for plan mode and Sonnet for act mode. However, _which_ Opus and Sonnet models exactly are being used is a different story... I can confirm that settingopusplanresults in my plan mode using Opus 4.1 and act mode using Sonnet 4. But I believe that's because I have this config in mysettings.jsontoo:So at least based on the payloads that Claude Code is sending to my status line script, it seems like it's working as I intended i.e. plan mode uses Opus 4.1 and act mode uses Sonnet 4. But hypothetically if
opusplanmode is set, butANTHROPIC_DEFAULT_SONNET_MODEL/ANTHROPIC_DEFAULT_OPUS_MODELare NOT, it's up to Anthropic which version exactly of those models will be used in the session... so I'm wondering if that's leading to some of the discrepancies here.Also FWIW, most LLMs are notoriously bad at knowing what model they are... so using the
/statusslash command, or checking the payloads sent to status line scripts, will be much more accurate in denoting the current model being used. I'm not sure of this, but I'm assuming that the outputs of/statusand the status line payloads will be more accurate than the UI values given the issues already identified in the2.0.0UII just confirmed that if I set
opusplaninsettings.json, but remove"ANTHROPIC_DEFAULT_SONNET_MODEL": "claude-sonnet-4-20250514", then plan mode still uses Opus 4.1 but act mode now uses Sonnet 4.5 instead of Sonnet 4It seems like this initial top line only gets rendered when the session starts and doesn't update in real time:
<img width="367" height="112" alt="Image" src="https://github.com/user-attachments/assets/a3e02d78-21c6-4d79-8552-5f9a478825a8" />
Also for @PaulRBerg 's issue, there's a rough edge with
opusplanmode that it doesn't automatically start your session in plan mode... which you can see bybypass permissions onbeing shown in your status line. If you were in plan mode you'd seeplan mode onin that same place instead. If you useshift+tabto cycle to plan mode, you should see the model correctly update to Opus in the status lineAt least from my experience,
opusplanonly works (i.e. uses Opus to plan, presents the plan to the user where they can approve or deny, and if they accept the plan it auto switches to Sonnet for implementation) if the session is already in "plan" mode set viashift+tab. It's definitely confusing 🤷Hi all, thanks for your feedback! As you might imagine, we are open to changing the UI based on the feedback we hear over the next few days, but I want to add some clarifications in the meantime.
Tabto control thinking.opusplansetting still works. You can manually set it in~/.claude/settings.jsonas pointed out above or use/model opusplan.ANTHROPIC_DEFAULT_OPUS_MODELandANTHROPIC_DEFAULT_SONNET_MODELcontrol which "opus" and "sonnet" modelsopusplanuses. In v2.0.0, the defaults for "opus" and "sonnet" are Opus 4.1 and Sonnet 4.5 respectively.opusplandoes not show up well after our change (shows up as a "custom model"). We will fix this issue in v2.0.1.Is this why you removed 'think' 'think hard' 'think very hard'? :/
Discord is already lit up with folks trying to revert to get this critical functionality back.
Thinking seems to help. But simple UI tasks like moving the position of two
CTAs it struggled with simple comprehension tasks. What would have taken
one attempt took half a dozen and honestly the frustration factor was real.
Previously I was doing complex refactors with Claude. Right now that seems
like light years away.
Unfortunately I don't know what my model settings were on the 1.x branch so
it's hard to do a scientific test.
Right now it feels like Claude's gone from 5 year experienced dev to
kindergarten since 2.0 release.
The new features and the crab logo are cool and all but if the core feature
of writing code suffers then it will push me and I assume others to use
competitors tooling. $100 a month per dev for Max so it's not a small cost.
More credits on Opus might help?
On Tue, 30 Sep 2025 at 07:53, Jack @.***> wrote:
Could you please take a look at my related issue #8449?
I believe the automatic model selection bug is directly related to this opusplan removal.
The bug caused my system to use expensive models (Opus) for trivial tasks without my
control, leading to excessive token consumption.
I found the workaround (manually setting opusplan in settings.json), which seem to resolved the issue. However, I'm now unfairly rate-limited due to a system bug.
My questions:
I understand bugs happen, but paying customers shouldn't be penalized with rate limits caused by system issues beyond their control. I'd appreciate the team's position on compensating affected users.
After use, it is possible that the diagnosis is rather than that it happens during the compact of the conversation
Thanks for the reply @dicksontsai
I played with Sonnet 4.5 for a while today, and yeah, it does seem a little better than Opus 4.1 in plan mode - or at least as good as Opus 4.1
May I suggest to change the wording in the model selection UI? It's currently worded like this:
<img width="750" alt="Image" src="https://github.com/user-attachments/assets/205239a8-d2d4-41af-ba9e-33544f67a08e" />
---
Which makes it seem like Sonnet 4.5 is like Sonnet 4.0, i.e., an execution guy. But Sonnet 4.5 is both a judicious planner and an execution guy. The current wording doesn't clearly communicate this.
You can use old models with the
--modelCLI option, but it seems that it will use Sonner 4.1 instead of 4.5 out of planning.<img width="1177" height="300" alt="Image" src="https://github.com/user-attachments/assets/eb12859f-e78e-4b19-9ca0-0705e8c10dba" />
Claude 2.0.2 seems to have restored the option for OpusPlan.
On Thu, 2 Oct 2025 at 17:13, Maksymilian Majer @.***>
wrote:
I've updated my VS Code extension but it still has the old references (I was also using the CLI too with
--model). It was working last week but this today when usingOpus Plan Modeit was defaulting my session to Opus and maxed my Opus limit for the week. (Max Plan)<img width="572" height="301" alt="Image" src="https://github.com/user-attachments/assets/b38baa4c-6a96-4a10-b7a0-4f1eec73855d" />
It seems like bug. As a max plan user I can use any model mentioned in docs by setting model manually and it works. It just model selection is broken.
except in real life practice, it's absolutely not the case. it might have been fine tuned on benchmarks, but Sonnet 4.5 is one of the worst model created so far. It is however fast and probably cheap for them to run. Reasoning is extremely limited. The whole claude code experience has also been tuned down (eg no more way to trigger thinking mode with keywords : think, think carefully, ultrathink etc).
Definitely a downgrade. "opusplan" was amazing in comparison.
@dicksontsai : suggestion for the future. Create /model: planmode option that allows user to define model for planning and model for execution. More choice = more happiness / fewer complaints.
Are we getting this feature or not? This is over a month old, and it's asking for functionality that already existed in a previous version. So did something break fundamentally?
Anthropic's runway
(As a result of running Opus in the cloud)
Yeah this mode should be restored–I miss it dearly. Played with the workarounds in the thread, but it doesn't seem to be very reliable. Hard to tell if its working at all.
@claude You have more money than many countries. Do better.
Hey @dicksontsai & Anthropic team, now that Opus 4.5 is live and also available Claude Code v2.0.51, can you please, please bring
opusplanback? 🙏<img width="500" src="https://github.com/user-attachments/assets/fe7ef283-87f7-46ff-a6f8-62f09bb8fa3c" />
I don't want to have to manually switch between models using
/model.The Opus-for-planning and Sonnet-for-execution combo was a killer feature.
Seriously... come on guys... give us opusplan!!! What is the holdup?!
The revenue earned from picking
/model opusand forgetting to switch to sonnet on execution far exceeds the tears in this thread.Buahaha, exactly :D was just activating /extra-usage (smart move to offer that) and looking up the ticket to add a vote on it :D
Cash rules everything around me (not solid software engineering practices)
Opus plan mode works fine. You just need to set it up as follows in the
.claude/settings.json.Substitute the model IDs for your providers' model IDs – I use bedrock.Below is video proof of it working.
https://github.com/user-attachments/assets/a39c985a-8679-4608-832c-5bc4e93b9a87
I haven't tested @navkast's solution, but users shouldn't have to guess if
opusplanworks. It should be clear that it works.I repeat - please bring back
opusplanmode!This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
Please keep active. When Sonnet 4.7 comes out, it would be helpful to be able to use Opus 4.5 for planning and Sonnet 4.7 for execution.
this feature still available, you guys just need to switch model in CLI session
/model opusplanyep, just check this page https://code.claude.com/docs/en/model-config
/model opusplan- Opus is active in Plan mode, otherwise Sonnet;/model haiku- Sonnet is active in Plan mode, everything else Haiku.How to check?
Use a
/contextcommand.Yeah I can confirm they've brought it back.
<img width="382" height="61" alt="Image" src="https://github.com/user-attachments/assets/cf51b13f-259d-4a7d-adc4-61d9adda9a03" />
However,
opusplanis not documented in the default window that appears when running/model:<img width="727" height="190" alt="Image" src="https://github.com/user-attachments/assets/86b29f67-053e-4dc8-8ceb-2eb4dad50260" />
So I've opened another issue to document this feature in the
/modeloptions: https://github.com/anthropics/claude-code/issues/26556This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.