/model can no longer apply a second model change or print a duplicate notice.
What's wrong with this entry?
A stale consent callback from /model can no longer apply a second model change or print a duplicate "Kept model as" notice. The picker now tracks whether it has already been answered and returns early if so.
- Both the
/modelcommand and the model-switch component carry a generation counter and an already-handled flag, checked before the model change is applied. - The user-facing strings moved into shared constants with no wording change.
Kept model as
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.234
Search field in the model picker
Both mention model
-
v2.1.236
Cancellable waits when
/modeltalks to a cloud sessionBoth mention model
-
v2.1.238
Model and effort switch warning now checks whether the cache is actually warm
Both mention model