Legacy Model Remapping — Clearer Warning and Opt-Out

When Claude Code automatically remaps a deprecated model ID to a current one, the warning now includes the model name being used and mentions the opt-out env var:

Before: ⚠ Claude Opus 4.7 has been updated to claude-opus-4-8.

After: ⚠ claude-opus-4-7 is automatically remapped to Claude Opus 4.8 (claude-opus-4-8). Set CLAUDE_CODE_DISABLE_LEGACY_MODEL_REMAP=1 to keep the requested model.

Also, the status-line model indicator now shows the same opt-out hint in shortened form: ⚠ Opus 4.7 remaps to Claude Opus 4.8. CLAUDE_CODE_DISABLE_LEGACY_MODEL_REMAP=1 opts out.

Evidence

Modified DCo() and new lzn() functions — search for "is automatically remapped to" and "CLAUDE_CODE_DISABLE_LEGACY_MODEL_REMAP=1 opts out"

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.182 →

The build it came inv2.1.182

18 Jun 2026 · 21 entries, this one is #8.

Either side of it

v2.1.181Older
v2.1.183Newer

Open the release →

Names in this entry

modelclaude-opus-4-8
Opus 5 is now the default Opus, with a 1M-context option in the model picker.
modelclaude-opus-4-7
Opus 5 is now the default Opus, with a 1M-context option in the model picker.
envCLAUDE_CODE_DISABLE_LEGACY_MODEL_REMAP
Set to 1 to prevent automatic remapping of Opus 4.0 and 4.1 to the current Opus version on the Anthropic API. Use when you intentionally want to pin an older model. The remap does not run on Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.