[BUG] /model default resolves to Opus 4.7 but UI picker shows Default = Sonnet 4.6
Status Fixed / completed
Reported on v2.1.92
Maintainer reply None cached
Activity 3 comments · opened Apr 18, 2026 · closed Apr 20, 2026
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?
switch model UI in VSCode extension mentions Sonnet as default, but sets to Opus 4.7
What Should Happen?
If default says it Sonnet 4.6, then it should switch model to Sonnet 4.6
Error Messages/Logs
Steps to Reproduce
open switch model ui and choose default - check in chat extension the model it switches to
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.92 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Cursor
Additional Information
_No response_
3 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
/model defaultresolving to Opus 4.7 while the VS Code extension UI picker labels Default as Sonnet 4.6 is an agent identity display mismatch — the user selects what they believe is "Sonnet 4.6 (default)" but the agent actually runs as Opus 4.7. The model that executes differs from the model the user believes they selected.This is the same class of silent model substitution documented in:
In all cases, the declared model configuration and the actual runtime model diverge without notification.
The three possible root causes:
/model defaultcommand and the UI picker are reading from different sources. The CLI command reads the current server default; the UI reads a cached/hardcoded label. They need to read from the same source./model defaultmay be returning the persisted model rather than the actual default.The fix: The "Default" option in the model picker should display the actual current default model identifier, not a hardcoded label. When the user selects Default, the agent should start on whatever model the current default is, and the UI should confirm which model that is.
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.