{"version":"2.1.222","anchor":"subagent-models-outside-the-allowlist-step-down-within-their","canonical_anchor":"subagent-models-outside-the-allowlist-step-down-within-their","heading":"Subagent models outside the allowlist step down within their family","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/subagent-models-outside-the-allowlist-step-down-within-their","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Subagent models outside the allowlist step down within their family\n\nSubagents asking for a disallowed model now drop to the newest allowed model in the same family.\n\n**What**\n\nA 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.\n\n**Details**\n\n- Only applies when a same-family allowed model exists; otherwise the old parent\/default fallback still runs.\n- Emits telemetry code `family_alias_stepped_down` and a matching warning log.\n\n**Evidence**\n\n`family_alias_stepped_down`\n\n- Area: Models\n- Names: `availableModels`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}