{"version":"2.1.251","anchor":"subagent-model-field-documents-its-fallback-order","canonical_anchor":"subagent-model-field-documents-its-fallback-order","heading":"Subagent model field documents its fallback order","tier":"use","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/subagent-model-field-documents-its-fallback-order","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Subagent `model` field documents its fallback order\n\nSubagent model field docs now spell out alias, raw id, inherit, and the default fallback.\n\n**What**\n\nThe `model` field for subagents now says it takes a model alias, a raw model ID, or `inherit`, and that leaving it unset uses a configured default subagent model, falling back to the parent conversation's model when none is configured.\n\n**Details**\n\n- The wording implies a separate default-subagent-model setting that applies to every subagent you do not pin.\n\n**Evidence**\n\n`uses the default subagent model when one is configured, else the parent's model`\n\n- Area: Subagents\n- Names: `inherit`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}