Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Rate LimitsArea: what it touches
Internal ChangesKind: in v2.1.242,
Internal ChangesSection of the release
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.
