[BUG] switch model itself

Status Fixed / completed
Maintainer reply None cached
Activity 5 comments · opened Feb 8, 2026 · closed Mar 8, 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?

When useing Claude Code, it switch to Opus 4.6 by itself

What Should Happen?

It should not switch the model. I want to decide, which model should be used.

Error Messages/Logs

none

Steps to Reproduce

Set Sonnet as model. Switch from one Chat to another an back again. Then Opus is selected

Claude Model

None

Is this a regression?

I don't know

Last Working Version

Version 1.1.2321 (495628)

Claude Code Version

1.1.2321

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/23900
  2. https://github.com/anthropics/claude-code/issues/20745
  3. https://github.com/anthropics/claude-code/issues/7341

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

pern0x · 6 months ago

Don't close this...
It's really annoying. There are a lot of triggers, which switch to opus 4.6 in claude code. Remove them please or make them optinal in the setting.

samirmsallem · 5 months ago

push, please fix asap.

The idea of using cheaper models for less complex tasks is great. This should be done automatically. However switching from Sonnet/Haiku to Opus without user approval is inacceptable.

My suggestion would be two flags that can be set:

CLAUDE_AUTO_MODEL_DOWNGRADE (default: true)
CLAUDE_AUTO_MODEL_UPGRADE (default: false)

pern0x · 5 months ago

For me it is fixed and did not happen again.

github-actions[bot] · 5 months ago

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.