`/model` switch warning fires after `/clear` but not on a fresh instance

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?

After running /clear, switching models via /model triggers the warning introduced in v2.1.108:

"This conversation is cached for the current model. Switching to Opus 4.7 means the full history gets re-read on your next message."

This warning does NOT appear when switching models on a brand new session (fresh restart, no prior conversation). It only appears after /clear has been run. Since /clear is supposed to wipe conversation history entirely, the two states should be equivalent from the warning's perspective, but they are not.

What Should Happen?

After /clear, the session state relevant to the /model warning should be equivalent to a fresh instance. No warning should appear.

Error Messages/Logs

Steps to Reproduce

1. Start a Claude Code session
2. Have any conversation
3. Run /clear
4. Run /model and switch to a different model

→ Warning appears despite empty context

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.114

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

Running on Ghostty terminal

Related Issues

• #48087