[BUG] Opus 4.5 showing in Claude Code CLI, but not showing in Claude Code VSCode extension
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
I am on Windows 11 ARM, Max 20x plan, CLI works with Opus 4.5, extension doesn't no matter how I reset and reinstall the extension with cache removed.
Extension version : anthropic.claude-code@2.0.46
Claude Code version: 2.0.69
I also tried to force it in the configuration of the vscode json file by changing the default model name. It fall back to Sonnet 4.5.
<img width="479" height="139" alt="Image" src="https://github.com/user-attachments/assets/09447d1f-1185-4482-88b3-671c41e134e2" />
What Should Happen?
Claude Code extension interface shall allow selection of Opus 4.5 instead of Opus 4.1.
Error Messages/Logs
Steps to Reproduce
Steps to Reproduce:
- Install Claude Code VS Code extension from marketplace
- Authenticate with Max plan account
- Open a project folder in VS Code
- Click the Spark icon to open Claude Code panel
- Start a new conversation (Ctrl+N)
- Open model picker via
/modelcommand or UI dropdown - Observe available models - Opus 4.5 is not listed (only shows Opus 4.1)
- Alternatively, set
"claudeCode.selectedModel": "claude-opus-4-5-20251101"in VS Code settings.json - Reload VS Code
- Start new conversation and send any message
- Receive error:
Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"messages.37.content.0.type: Expected `thinking` or `redacted_thinking`, but found `tool_use`. When `thinking` is enabled, a final `assistant` message must start with a thinking block..."}}Expected Behavior:
Opus 4.5 should appear in the model picker and work correctly, matching the CLI behavior.
Actual Behavior:
- Opus 4.5 not shown in model picker
- Manually setting the model string causes API errors related to extended thinking
Workaround:
Using CLI directly (claude --model claude-opus-4-5-20251101) works correctly.
Additional Context:
- Disabling extended thinking does not resolve the issue
- Clean reinstall of extension and clearing ~/.claude folder does not resolve
- CLI on same machine with same account works perfectly with Opus 4.5
Claude Model
Opus
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.0.69
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
13 Comments
Found 1 possible duplicate issue:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This is not the same issue, as this is strictly with the VS code extension.
I am experiencing the same issue (also on Windows 11 ARM)
Update:
The issue persists even with a fresh installation with the latest vscode extension, along with Claude Code CLI version 2.0.76.
in command palette > Claude Code Log-outlog-out extension, log-in again.
Default option shows up.
But, an hour or two, a day?
After some time passes, it's gone again.
-__-;
@srb-sd , I tried many times including logging out and back in. Still no default options for me. Just to confirm are you also on Windows on Arm?
@nocdoggo
I'm using Intel Win, but the system type doesn't seem to be involved in causing the issue.
The same thing happens with Claude Code CLI (similar to what happens with CC extensions).
1st workaround ; exit Claude Code, delete ~\.claude folder, ~\claude.json file, run claude~
2nd workaround ; all remove, re-install...
--> default option back --> but soon, its gone.
CC extension ; log-out, log-in ----> default option back, or log-out, and remove extension, re-install --> default option is back.
But soon, the default menu option disappears again.
In my case, the default choice becomes opus (which is a very negative thing).
Just make sure to check the current model with the /model command every time you use it.
This is the most practical workaround.
It's sad.
So, I don't know why the decision made by the Claude team is to not update the extension beyond 2.0.46 for native windows on arm. The only solution is to install x64 VSCode and then install the extension. However, this runs into many many many issues due to simulation. We are yet to hear from the Claude team regarding anything new about Windows on ARM situation.
We unpublished the universal package as a workaround for https://github.com/microsoft/vscode/issues/276673 (see also https://github.com/anthropics/claude-code/issues/11868).
The VSCode issue has been resolved, looking to bring this package back.
@blois , oh crikey! We got a hooman on this matter. Thanks a lot!
Just another feedback, not that related to this ticket. The default windows installation method for claude code Cli is also broken on Windows on ARM. It would attempt to install the x64 variant. The only solution is still performing the installation via npm.
Yes, we're working on that as well. The node.js version of the VSCode extension should be returning tomorrow. We still have some work to fix the native binaries on ARM, which is what you're running into.
Version
2.1.15now includes a universal extension again.This 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.