Claude Code telemetry now separates cache-write token usage by lifetime
Claude Code v2.1.300, released October 14, adds separate cache-write token counts for five-minute and one-hour lifetimes to its OpenTelemetry api_request event. The release does not announce a cache-price or usage-limit change.
SessionWatcher editorial · Published · Updated · Source announcement: 2026-10-14
Related guide: How to check your Claude Code usage
New cache-write usage fields
Claude Code v2.1.300, released October 14, adds a cache-write token breakdown to its OpenTelemetry api_request event. The new fields are cache_creation_5m_tokens and cache_creation_1h_tokens, separating cache writes by lifetime.
The addition gives developers using that telemetry separate counts for five-minute and one-hour cache writes, rather than leaving those lifetimes undifferentiated in the new breakdown.
Sources: v2.1.300
Telemetry, not a pricing change
The announced change is to the api_request telemetry event. This release note does not announce different cache-write prices, new plan allowances or changed reset schedules. It also does not describe adding this breakdown to the /usage screen.
Sources: v2.1.300
AI assisted reporting, checked against the linked official sources. Source pages checked 2026-10-14. Editorial process and corrections.