{"version":"2.1.314","anchor":"hook-type-permission-denial-for-model-overrides-model-knowl","canonical_anchor":"hook-type-permission-denial-for-model-overrides-model-knowl","heading":"Model lookups treat overridden model names differently","tier":"internal","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/hook-type-permission-denial-for-model-overrides-model-knowl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Model lookups treat overridden model names differently\n\nWhen a model name is an override, Claude Code now skips its first lookup when finding stored details about that model\n\n**What**\n\nClaude Code keeps stored details about each model. To find them it tries several possible matches in turn. When a model name counts as an override, it now skips the first of those and starts with the next one.\n\n**Why**\n\nThis may change which stored details are used for overridden models.\n\n- Area: Models\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}