Subagents asking for a disallowed model now drop to the newest allowed model in the same family.
What's wrong with this entry?
A subagent or teammate asking for a model that is not in availableModels now falls to the newest allowed model in the same family rather than straight to the parent or default model.
- Only applies when a same-family allowed model exists; otherwise the old parent/default fallback still runs.
- Emits telemetry code
family_alias_stepped_downand a matching warning log.
family_alias_stepped_down
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