{"version":"2.1.267","anchor":"new-channel-scope-for-usagespend-limit-messaging","canonical_anchor":"new-channel-scope-for-usagespend-limit-messaging","heading":"Rate-limit overage responses can now be scoped to a channel","tier":"notice","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-channel-scope-for-usagespend-limit-messaging","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Rate-limit overage responses can now be scoped to a channel\n\nUsage-limit warnings can now say the limit applies to a channel, not just the whole organization\n\n**What**\n\n- A new `overageScope: \"channel\"` field was added to rate-limit\/overage status, read from the `anthropic-ratelimit-unified-overage-scope` response header when it equals `channel`, replacing a boolean overage flag derived from a single header.\n\n- The usage\/spend-limit warning text now branches on this scope, showing \"channel's monthly spend limit\" or \"channel's monthly usage limit\" instead of the general org-wide message when the scope applies.\n\n**Why** Lets Claude Code tell users precisely which quota is running low or exhausted, a shared channel's limit versus the whole organization's, so the warning is more actionable.\n\n- Area: Rate Limits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}