{"version":"2.1.251","anchor":"subagents-can-default-to-a-configured-model-instead-of-the-s","canonical_anchor":"subagents-can-default-to-a-configured-model-instead-of-the-s","heading":"Subagents can default to a configured model instead of the session model","tier":"use","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/subagents-can-default-to-a-configured-model-instead-of-the-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Subagents can default to a configured model instead of the session model\n\nSubagents without an explicit model now use your configured default subagent model.\n\n**What**\n\nWhen a Task worker is launched without an explicit model, it now falls back to a configured default subagent model if one is set, and only then to the model of the session that spawned it. An agent definition's own model setting still wins over both.\n\n**Details**\n\n- Precedence: agent-definition setting, then configured default subagent model, then inherited session model.\n- With no default configured, behaviour is unchanged from plain inheritance.\n\n**Evidence**\n\n`otherwise omit it so the worker uses the default (the session model, unless a default subagent model is configured)`\n\n- Area: Subagents\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}