{"version":"2.1.323","anchor":"rate-limit-classification-overage-on-the-overage-window-no","canonical_anchor":"rate-limit-classification-overage-on-the-overage-window-no","heading":"Rate limits are sorted into types differently when overage is in use","tier":"notice","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/rate-limit-classification-overage-on-the-overage-window-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Rate limits are sorted into types differently when overage is in use\n\nA rate limit counts as overage only when overage is in use and the limit is not the overage limit itself\n\n**Unclear.** Which rate-limit messages change as a result is not stated.\n\n**What**\n\nA rate limit caps how much you can use Claude in a period of time. Overage is extra usage beyond your plan's normal allowance. Claude Code sorts each rate-limit status into a type, and it has changed two parts of how it does that:\n\n- Overage type: a status now counts as overage only when overage is in use and the limit hit is not the overage limit itself. Before, overage being in use was enough.\n\n- Unknown limit kind: a status that does not say which kind of limit it is now goes through the normal checks. Before, it was always put in a catch-all type.\n\n**Why**\n\nThis can change which rate-limit message or handling you see when you hit a limit.\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}