{"version":"2.1.319","anchor":"rate-limit-headers-daily-cap-pause","canonical_anchor":"rate-limit-headers-daily-cap-pause","heading":"Claude Code recognises when your organization's usage is paused by a daily cap","tier":"notice","area":"Usage & Limits","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/rate-limit-headers-daily-cap-pause","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Claude Code recognises when your organization's usage is paused by a daily cap\n\nA new daily-cap pause for organizations gets its own messages, stops extra-usage offers, and is exposed to SDK programs as dailyCapPaused\n\n**Unclear.** It is not clear whether anything is shown to you yet when a daily cap pause happens.\n\n**What**\n\nClaude Code can now tell when usage is paused for your whole organization because of a daily cap. It treats this differently from an ordinary rate limit, which is a limit on how much you can use in a period.\n\n- The rate-limit reader checks a new response header, `anthropic-ratelimit-unified-overage-daily-cap-paused`. When it is `true`, it sets `dailyCapPaused` on the limit status, including on refused requests.\n\n- When an API `rate_limit` error carries `quotaLimits.dailyCapPaused` set to true, the pause gets the cause `daily_cap` instead of `usage_limit` or `rate_limited`. Which parts of Claude Code act on the new cause was not traced.\n\n- A paused `\/goal` now reads \"Goal paused \u00b7 usage is paused for your organization\". A message \"Usage is paused for your organization. For help, please contact support.\" also appears.\n\n- The usual rate-limit message is skipped when `dailyCapPaused` is true.\n\n- While the cap is paused, the offer to buy extra usage does not appear and the automatic arming for rate limits stops. The extra-usage flow also stops early when `daily_cap_notice` is set.\n\n- A plan or limit check now also requires `dailyCapPaused` not to be true.\n\n- In the `api_error` description, `rate_limit_info` for `usage_limit_reached` now includes `dailyCapPaused`, which is true when usage is paused for the organization. Programs built on the SDK (the kit for driving Claude Code from your own code) can read it.\n\n- A quota error is now ignored when the caller passes `onlyLimiterRefusals` and the status is not `rejected`.\n\n- The client defines a new header name, and how it is used was not traced.\n\nSeparately, the spend-limit proxy now tries a second read when the caps come back empty. Its 429 (too many requests) message now says \"spend limit reached\" with a reset date.\n\n**Why**\n\nIf your organization hits a daily cap, you get a clear reason, and you are not offered extra usage that would not help. Programs on the SDK can tell this pause apart from other limits.\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}