{"version":"2.1.234","anchor":"rate-limit-prompts-resolve-model-aliases-to-the-model-that-a","canonical_anchor":"rate-limit-prompts-resolve-model-aliases-to-the-model-that-a","heading":"Rate-limit prompts resolve model aliases to the model that actually answers","tier":"notice","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/rate-limit-prompts-resolve-model-aliases-to-the-model-that-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Rate-limit prompts resolve model aliases to the model that actually answers\n\nRate-limit prompts now resolve model aliases, so you get fewer misdirected limit warnings.\n\n**What**\n\nPrompts and warnings tied to a specific model now look through aliases: `opusplan` and `opusplan[1m]` count as Opus, `haiku` counts as Sonnet. You get fewer confirmations and fewer misdirected limit warnings when running on an alias.\n\n**Details**\n\n- Replaces three separate yes\/no alias checks: the main-model confirmation loop now skips confirmation for aliased models, the seven-day Opus and Sonnet limit notices no longer fire when the alias already resolves to that family, and the extra-usage upsell is suppressed for aliased models.\n- Any model that is not one of those aliases resolves to nothing and behaves as before.\n\n**Evidence**\n\n`opusplan[1m]`\n\n- Area: Rate Limits\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}