[BUG] VSCODE EXTENSION: switching to Sonnet model still gets you opus
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?
every time I try to select Sonnet using /model select from VSCode extension drop down. I select Sonnet but get Opus. depsite the dropdown saying Sonnet.
<img width="720" height="210" alt="Image" src="https://github.com/user-attachments/assets/80f3de5b-9929-4547-bc91-d3ed9c902e34" />
you can see that it just uses Opus either way... and worst of all it uses the 1m context window Opus for Sonnet... <img width="746" height="315" alt="Image" src="https://github.com/user-attachments/assets/d949b19e-fe05-478f-a202-4359ab978dd9" /> so it used up my whole 5-hr allotment in 10 mins when I thought I was being careful by setting it to Sonnet.
What Should Happen?
Sonnet should actually use Sonnet and I should get reimbursed.
Error Messages/Logs
Steps to Reproduce
Toggle is over .. see pictures included. /model select
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.76
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗