Advisor results now normalise unknown stop reasons and route refusals into refusal handling.
What's wrong with this entry?
Results coming back from an advisor tool now map their stop reason through a known list, including compaction, refusal and context-window-exceeded, and anything unrecognised becomes unknown instead of being passed through. A refusal reason triggers the refusal handling path.
model_context_window_exceeded: !0
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.224
Advisor entry added to Managed Agents multiagent rosters
Both mention advisor
-
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