Claude Code v2.1.228 ·
Fallback models are reflected in the reported model
If a request falls back to another model, you now see the model that actually answered.
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ModelsArea: what it touches
Bug FixesKind: in v2.1.228,
What probably matters to youSection of the release
What
When a request falls back to a different model mid-stream, the model shown to the client now matches the one that actually answered.
Details
- A streamed content block of type "fallback" sets the accumulated message's model to the fallback target.
- The gateway's event re-encoder rewrites the model on the opening
message_start event when an override model is in play.
Evidence
content_block.type === "fallback"
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.228 →
