[BUG] settings.json model preference ignored on v2.1.111 — sessions default to Opus 4.7 despite explicit model pin
What's Wrong?
~/.claude/settings.json contains "model": "claude-opus-4-6" but claude --resume on v2.1.111 starts the session on Opus 4.7.
What Should Happen?
If the user has an explicit model preference in settings.json, the session should respect it. Users should be able to pin their model via configuration without having to run /model on every resume.
Steps to Reproduce
- Set
"model": "claude-opus-4-6"in~/.claude/settings.json npm install -g @anthropic-ai/claude-code@2.1.111claude --resumeon any existing session- Observe: session starts on Opus 4.7, not 4.6
Impact
Opus 4.7 uses adaptive thinking which consumes Q5h quota at approximately 2.4x the rate of 4.6 (measured across 71 API calls, cross-validated by independent gateway proxy data). Users who have pinned 4.6 in settings.json to avoid this cost increase are silently overridden.
See community discussion with metered data: https://github.com/cnighswonger/claude-code-cache-fix/discussions/25
Claude Code Version
2.1.111
Platform
Anthropic API (subscription, Max 5x)
Operating System
Ubuntu Linux
Terminal/Shell
bash
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗