claude-code - 💡(How to fix) Fix [BUG] --resume doesn't use the model from the original session [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56384Fetched 2026-05-06 06:29:32
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • 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?

When starting a session with a specific model such as claude --model='claude-opus-4-6[1m]' then later you resume the session using claude --resume <ID> without explicitly passing the model again --model='claude-opus-4-6[1m]', the model used in the resumed session defaults to claude code's default model (Opus 4.7 1M).

What Should Happen?

Since the session was started with a specific model I'd expect resumption to continue using such model.

Error Messages/Logs

Steps to Reproduce

  1. Start a session with claude --model='claude-opus-4-6[1m]'
  2. Do anything to trigger the model
  3. Run /exit
  4. Resume the session with claude --resume <ID>
  5. Note the model used is not the model the original session started with

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

1.0.126

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

Passing the --model parameter when resuming a session with claude --resume <ID> may fix the issue by ensuring the original model is used.

Guidance

  • Verify that the model is correctly specified when starting the session and that it is saved correctly for resumption.
  • When resuming the session, try explicitly passing the model again using claude --resume <ID> --model='claude-opus-4-6[1m]' to see if it resolves the issue.
  • Check the documentation for any specific requirements or limitations on resuming sessions with custom models.
  • Test resuming a session with a different model to see if the issue is specific to the claude-opus-4-6[1m> model.

Example

claude --resume <ID> --model='claude-opus-4-6[1m>'

Notes

The issue may be related to how the model is stored or retrieved when resuming a session. Without more information on the internal workings of Claude Code, it's difficult to provide a definitive solution.

Recommendation

Apply workaround: Pass the --model parameter when resuming the session, as it ensures the original model is used and may resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING