You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Severe quality degradation despite /model showing Opus - possible silent model mismatch #13943
I have searched existing issues and this hasn't been reported yet
This is a single bug report (please file separate reports for different bugs)
I am using the latest version of Claude Code
What's Wrong?
Since approximately 3 days ago, Claude Code shows severe quality degradation in following basic instructions, despite /model command confirming Opus is active.
Symptoms:
Ignores explicit file targets (e.g., "add to meta.json" → edits ai-research.json instead)
Claims context is lost even though the text was just provided
Repeatedly misquotes user input when asked to repeat it
Doubles down on errors instead of re-reading instructions
Behavior matches reports of silent Sonnet fallback, but /model still shows Opus
Relation to #3434
This may be related to #3434 (silent fallback to Sonnet), but with an additional issue: the /model command does not reflect the actual model being used. The UI/CLI says Opus, but behavior suggests otherwise.
Before (3+ days ago):
Instructions followed correctly
Same workflow worked without issues
After:
Simple tasks fail repeatedly
Must start new chats constantly
Even first message in fresh chat shows degraded behavior
What Should Happen?
If /model shows Opus, responses should reflect Opus-level instruction following.
Request
Please investigate whether there's a mismatch between displayed model and actual model being served.
Error Messages/Logs
Steps to Reproduce
Give clear instruction with explicit file target: "add X to meta.json"
Claude edits wrong file or misinterprets completely
Check /model → shows Opus
Behavior does not match Opus capabilities
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.
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.
Activity
github-actions commentedon Jan 13, 2026
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.
github-actions commentedon Feb 14, 2026
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
github-actions commentedon Feb 21, 2026
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.