[FEATURE] Add Support for opusplan Model in VSCode Extension
Open 💬 19 comments Opened Jan 31, 2026 by Josiah1
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
Currently, Claude Code for VSCode only supports a Haiku, Sonnet and Opus models. The smart selection model: opusplan, which offers advanced switching between sonnet and opus, is not available in the model selection dropdown.
<img width="530" height="206" alt="Image" src="https://github.com/user-attachments/assets/e3675e4f-edce-4396-91f7-6961f7a0ecd0" />
Proposed Solution
Add "opusplan" as an option in the model selector dropdown within the Claude Code VSCode extension.
Implementation would include:
- Add the opusplan identifier to the available models list
- Configure the extension to use the Opus Plan API endpoint when selected
- Update any model-specific settings or configurations
The user experience would be:
- Open model selector in Claude Code for VS Code
- See "opusplan" listed alongside other models
- Select it to use opusplan for all subsequent interactions
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
API and model interactions
Use Case Example
_No response_
Additional Context
_No response_
19 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
No. The issues you listed are related to the CLI tool, not to VS Code Extension
I am eagerly anticipating the OpusPlan feature in the VSCode Claude Code extension. It promises to be a highly valuable addition.
Unfortunately, it seems that no official boys care here. They have added a "stale". No hope.
This would greatly improve DX and make the extension on par with the CLI tool. I'm sure it would help with resource utilization on the Anthropic side as well as fewer requests would be directed to Opus for the implementation aspect of the development cycle.
+1. Very useful
please add this feature.
+1
<img width="725" height="352" alt="Image" src="https://github.com/user-attachments/assets/938545f6-2b72-486c-bdf6-501d00757ee0" />
Looks like this has been added. can anyone verify?
What version of the extension do you have? I just updated to version 2.1.76 in VSCode, but no change other than seeing Opus 1m is now the "default" model.
<img width="637" height="291" alt="Image" src="https://github.com/user-attachments/assets/8440b91f-2546-40d5-b37d-9665838ca9ca" />
It's v2.1.78 as of today.
I've just upgraded to this and still don't see the 'Opus Plan Mode' option 😔
(VS Code 1.111.0, Claude Code for VS Code 2.1.78, MacOS 26.3, Claude Pro user)
<img width="832" height="313" alt="Image" src="https://github.com/user-attachments/assets/1dbae47c-ae1b-4b61-8001-990c329cc514" />
For me, it is only visible in the model selection, after setting
opusplanas the default model.Problem solved! I managed to get the option to appear by adding this to my
settings.jsonin my user dirConfirming this workaround works, but would be nice if it was supported out of the box like the CLI.
For those that may be struggling, hopefully the below steps help.
~/.claude/settings.jsonfile (%UserProfile%/.claude/settings.jsonon Windows) to do this globally. If you only want to enable this for your current project, open the.claude/settings.jsonfile in your project."model": "opusplan"to the file or change the existing setting if it exists to set the default model used when opening up the extension (applies to CLI as well).To clarify, your
settings.jsonshould look like this as an example with the model being a root level setting and not nested under some other complex settings object:Yes:
No:
The next time you type
/model, you should see the below.<img width="565" height="303" alt="Image" src="https://github.com/user-attachments/assets/9a176977-e302-49cf-9595-0a955ff9ffa1" />
opusplan+ Bypass permissions conflict in VSCode extension — no visual feedbackBeyond just adding
opusplanto the dropdown, there's a deeper UX issue worth addressing:In the VSCode extension,
opusplanis fundamentally incompatible with Bypass permissions mode (the preferred mode for uninterrupted work). The two modes are mutually exclusive:opusplansilently falls back to Sonnet the entire sessionThere's also zero visual feedback when
opusplanis active. No indicator of which model is actually running. The user has no way to verify whether Opus ever ran, which completely erodes trust in the feature.Current workaround (manual):
This is exactly what
opusplanis supposed to automate — but in the VSCode extension, the user has to do it manually with no help from the alias.Expected behavior:
opusplanshould work seamlessly with Bypass permissions (Opus for the internal planning phase, then auto-switch to Sonnet for execution), or the extension should at minimum clearly communicate thatopusplanrequires Plan mode to function and explain the tradeoff.I really hope they add this, it's really clunky to have to
bad ux especially when the option already exists in the cli
are there any recent workarounds for this, or is the bypass permissions / opus plan conflict still happening?
I think you can use a prompt to achieve similar results
<img width="569" height="184" alt="Image" src="https://github.com/user-attachments/assets/2d9232cf-63f5-434e-96f3-f94dbf4245c0" />
<img width="937" height="110" alt="Image" src="https://github.com/user-attachments/assets/05db0a5e-cb87-4d19-bce1-adc72de80785" />