You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Model SwitchingArea: what it touches
New FeaturesKind: in v2.1.251,
New FeaturesSection of the release
What
A model switch requested over the control bridge no longer has to resolve on the spot. If the verdict is still outstanding, the bridge replies at once that the switch is pending, waits up to 8 seconds, then sends a follow-up system notice saying the pending switch was applied or failed.
Details
The pending reply reads: "This model switch is still pending (an earlier model request or a PreModelSwitch hook has not finished); it will apply when that completes unless it is refused".
The follow-up is "The pending model switch was applied" or "The pending model switch failed".
The deadline can in principle be supplied per request, but nothing in the build sets it, so the built-in 8000ms default always applies.
Typical causes of a pending verdict are an earlier model request still in flight or a PreModelSwitch hook that has not returned.
Evidence
This model switch is still pending (an earlier model request or a PreModelSwitch hook has not finished); it will apply when that completes unless it is refused
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded PreModelSwitch and PostModelSwitch hook events (block, confirm, or annotate a model switch); SessionStart resume hooks now receive…
