Fallback notices now say only that one response came from another model; your session model is unchanged.
What's wrong with this entry?
When a request falls back to another model, the notice explains that only that response came from the other model, and the session model display marks the switch as automatic.
- The old "Switched to X" wording is gone; the notice now says the response was generated or completed by the other model and that the session model is unchanged.
/statusand the model display append a note that the model was automatically switched.- The fallback notice is carried into the extracted last-assistant-response text with a ⚠ prefix.
This response was generated by ${n} instead. Your session model is unchanged.
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.221
/status shows a "Session kind" row
Both mention status
-
v2.1.228
Settings problems split into notices and genuinely invalid entries
Both mention status
-
v2.1.229
Version bumped to 2.1.229
Both mention status