{"version":"2.1.284","anchor":"model-family-aliases-resolve-to-the-first-listed-model-not","canonical_anchor":"model-family-aliases-resolve-to-the-first-listed-model-not","heading":"Model aliases like opus now pick the first matching model in a configured list","tier":"notice","area":"Models","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/model-family-aliases-resolve-to-the-first-listed-model-not","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Model aliases like opus now pick the first matching model in a configured list\n\nWith a configured model list, opus, sonnet and haiku now map to the first model of that family in the list, not the canonical claude- ID\n\n**Unclear.** It is not clear where the configured model list comes from or which features use this lookup.\n\n**What**\n\nWhen Claude Code has a configured list of models, it turns the aliases `opus`, `sonnet` and `haiku` into a model ID from that list. Each alias now maps to the first entry of that family in the list.\n\nBefore, Claude Code preferred the canonical ID of the family, such as a `claude-` name or a dated ID, and only fell back to other entries when no canonical one was present.\n\n**Why**\n\nIf you use a custom model list, for example through a gateway, the order of the list now decides which model an alias like `opus` uses. Check that the model you want comes first in its family.\n\n- Area: Models\n- Names: `opus`, `sonnet`, `haiku`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}