{"version":"2.1.311","anchor":"model-name-resolution-no-longer-special-cases-the-1m-suffix","canonical_anchor":"model-name-resolution-no-longer-special-cases-the-1m-suffix","heading":"Asking for the 1M-context model may give a different model name","tier":"notice","area":"Models","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/model-name-resolution-no-longer-special-cases-the-1m-suffix","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Asking for the 1M-context model may give a different model name\n\nOne rule that removed the [1m] suffix from a model name is gone, so the suffix is now added in those cases\n\n**Unclear.** Which accounts or setups met the conditions of the removed rule is not stated.\n\n**What**\n\nSome models have a version with a 1-million-token context window (how much text Claude can hold at once), marked by a `[1m]` suffix on the model name. When Claude Code turns a short model name into a full one, one rule used to strip the `[1m]` suffix under certain conditions. That rule is gone, and the suffix is now added in those cases.\n\n**Why**\n\nSome people asking for the 1M-context version may now get a different model name than before.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}