Requests carry fields for a fallback model used after a refusal, with nothing you can set.
Refusal-fallback metadata including fallback model, lane, credit code and original-model stamps is plumbed into requests, with no user-facing control.
What's wrong with this entry?
Requests now carry a block of fields describing a fallback used after a model refusal, including the fallback model, its lane, a credit code and mint details, and stamp fields recording the original model, category, trigger and request id. Plumbing for that path; nothing here is user-settable.
refusalFallbackModelLane: "visible"
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