When a turn falls back to a different model after a refusal, the display now shows the model actually used.
What's wrong with this entry?
When a turn falls back after a model refusal, the agent's displayed model is rewritten to the model actually used, and the fallback message now carries a scope.
- A new agent event kind propagates turn effort together with the turn model.
- The async-agent reader applies system/model_refusal_fallback by rewriting the agent's model rather than leaving the old one on screen.
- The optional scope field was added at three emit sites and in the parser.
agent-turn-effort
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.220
Opus 5 is skipped when the client cannot see model entitlements
Both mention model fallback
-
v2.1.220
Refusal fallback no longer picks Opus 5 when entitlements are unknown
Both mention model fallback
-
v2.1.227
Advisor calls carry prior turns and a refusal fallback
Both mention model fallback