{"version":"2.1.310","anchor":"early-warning-rate-limit-headers-now-carry-per-window-status","canonical_anchor":"early-warning-rate-limit-headers-now-carry-per-window-status","heading":"Usage limits now track a status for each time window","tier":"notice","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/early-warning-rate-limit-headers-now-carry-per-window-status","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Usage limits now track a status for each time window\n\nClaude Code now records a status for the five-hour and seven-day usage limits: allowed, allowed with a warning, or rejected\n\n**Unclear.** Whether this per-window status changes anything shown to you is not stated.\n\n**What**\n\nYour usage is limited over set time windows, such as five hours and seven days. Claude Code now reads a status the server sends for each window, `anthropic-ratelimit-unified-5h-status` and `anthropic-ratelimit-unified-7d-status`, and records it alongside the threshold you have passed. The status is one of:\n\n- allowed\n\n- allowed with a warning\n\n- rejected\n\nThe overage window does not take a status. Claude Code also reacts when a window's status or threshold moves.\n\n**Why**\n\nClaude Code is starting to read the server's own verdict on each limit window instead of working only from how much you have used.\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}