{"version":"2.1.314","anchor":"model-alias-and-override-resolution-reworked-with-model-ove","canonical_anchor":"model-alias-and-override-resolution-reworked-with-model-ove","heading":"Model aliases now follow availableModels and modelOverrides through one check","tier":"notice","area":"Models","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/model-alias-and-override-resolution-reworked-with-model-ove","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Model aliases now follow availableModels and modelOverrides through one check\n\nTurning a model alias into a specific model now checks your availableModels and modelOverrides settings in one shared place\n\n**Unclear.** Whether this new check is switched on in this release is not shown.\n\n**What**\n\nAn alias is a short model name that Claude Code turns into a specific model. That step now runs through one shared check that applies two settings:\n\n- `availableModels`, the list of models people are allowed to pick\n\n- `modelOverrides`, which maps model IDs to your provider's own IDs\n\nClaude Code can also map a custom model ID back to the standard model it stands for. The context window (how much text the model can take in at once) is worked out differently in one new case. When no `availableModels` entry matches an allowed model, `enforceAvailableModels` reports \"enforceAvailableModels: no availableModels entry expands to an allowed model\".\n\n**Why**\n\nIf your organisation sets these settings, this may change which model a session ends up using.\n\n- Area: Models\n- Names: `availableModels`, `modelOverrides`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}