Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Rate-limit telemetry records every window, not just the tightest one

Under the hood
Useful2 Signal3
Rate Limits

Usage telemetry now records every rate-limit window separately, including seven-day and overage figures.

What

Session telemetry now carries a per-window utilization breakdown with optional five_hour, seven_day and seven_day_overage_included entries, each holding a utilization number and a reset time, taken from the rate-limit headers on responses.

Details
  • Utilization can exceed 1, for example when a lower-priority episode runs past the 5-hour limit.
  • Events fire when a window's rounded percentage or its reset time moves, not only when the overall status changes.
  • The field is always absent for API-key, Bedrock and Vertex sessions, and only appears once a response carrying the headers has been seen.
  • The existing overall overage status is unchanged.
Evidence

unifiedWindows

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.242 →