{"version":"2.1.222","anchor":"subagent-model-fallback-says-why-it-fell-back","canonical_anchor":"subagent-model-fallback-says-why-it-fell-back","heading":"Subagent model fallback says why it fell back","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/subagent-model-fallback-says-why-it-fell-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Subagent model fallback says why it fell back\n\nWhen a subagent can't use its requested model, you now see why it fell back.\n\n**What**\n\nWhen a subagent cannot get the model it asked for, the notify callback now carries a reason distinguishing a same-family step-down from inheriting the parent's model, and the message shown downstream differs accordingly.\n\n**Details**\n\n- Reason is either family_step_down, meaning a fallback within the same model family was picked, or parent_inherit, meaning the subagent fell back to the parent session's model.\n\n**Evidence**\n\n`family_step_down`\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}