{"version":"2.1.280","anchor":"rate-limit-banner-is-now-cross-checked-against-the-actual-li","canonical_anchor":"rate-limit-banner-is-now-cross-checked-against-the-actual-li","heading":"Rate-limit banner is now cross-checked against the actual limit type before rendering","tier":"internal","area":"Usage & Limits","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/rate-limit-banner-is-now-cross-checked-against-the-actual-li","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Rate-limit banner is now cross-checked against the actual limit type before rendering\n\nClaude Code now checks a rate-limit warning's wording against the real limit type before showing it\n\n**What**\n\nWhen Claude Code hits a usage limit, it shows a banner warning (like \"You've hit your session limit\"). A new internal check now reads the wording of that message, works out which kind of limit it's talking about (session, weekly, or model-specific), and compares that against the actual limit type reported by the API.\n\n- If the two match, the banner is shown as before.\n\n- If they don't match, the banner is suppressed and not shown.\n\n**Why**\n\nThis prevents a mismatched or stale warning banner from being displayed, for example one that talks about a session limit when the real limit that was hit is a weekly or model-specific one. It should make rate-limit banners more trustworthy when they do appear.\n\n- Area: Usage & Limits\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}