{"version":"2.1.251","anchor":"subagent-model-resolution-now-records-where-the-model-came-f","canonical_anchor":"subagent-model-resolution-now-records-where-the-model-came-f","heading":"Subagent model resolution now records where the model came from","tier":"internal","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/subagent-model-resolution-now-records-where-the-model-came-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Subagent model resolution now records where the model came from\n\nSubagent model choice now records where the model came from, not just its name.\n\n**What**\n\nPicking a subagent's model now tracks the source of the request separately from the model name, distinguishing tool overrides, the agent's own frontmatter, the `CLAUDE_CODE_SUBAGENT_MODEL` environment variable, and defaults.\n\n**Details**\n\n- The existing model-resolution telemetry gained outcomes for a model family alias being stepped down, an override being dropped, and a family mismatch.\n- Aimed at correctness of which model a subagent ends up on; nothing new is surfaced in the UI.\n\n**Evidence**\n\n`subagent_model_resolve`\n\n- Area: Subagents\n- Names: `CLAUDE_CODE_SUBAGENT_MODEL`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}