{"version":"2.1.280","anchor":"rate-limitoverage-info-gained-monthly-and-channel-scoped-ov","canonical_anchor":"rate-limitoverage-info-gained-monthly-and-channel-scoped-ov","heading":"Rate-limit\/overage info gained monthly and channel-scoped overage tracking, plus a 'grace' state","tier":"notice","area":"Usage & Limits","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/rate-limitoverage-info-gained-monthly-and-channel-scoped-ov","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Rate-limit\/overage info gained monthly and channel-scoped overage tracking, plus a 'grace' state\n\nRate-limit status data now includes monthly and channel overage utilization plus a grace-period flag\n\n**Unclear.** The finding does not say whether or when this new data is actually surfaced to users in `\/usage` output.\n\n**What**\n\nThe internal data used for `\/usage`-style rate-limit reporting has grown three new fields:\n\n- `overagePeriodMonthly.utilization` \u2014 how much of a monthly overage allowance has been used\n\n- `overagePeriodChannel.utilization` \u2014 how much of a channel-scoped overage allowance has been used\n\n- `rateLimitGraceActive` \u2014 a flag marking whether a grace period is currently active\n\nThese sit alongside the overage fields that already existed in this data shape.\n\n**Why**\n\nThis gives Claude Code more detail to draw on when reporting usage and rate limits, including tracking overage separately by month and by channel, and recognizing when an account is in a grace period rather than fully rate-limited.\n\n- Area: Usage & Limits\n- Names: `\/usage`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}