Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.265 ·

New startup_timing telemetry field on system init message

System init message can now carry cold-start timing data for hosted CCR sessions

Under the hood No documentation found Internal Changes
JSON All of v2.1.265
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release

Unclear What "CCR" stands for and what specifically consumes this telemetry isn't stated.

What

The system init message sent at the start of a session can now include a startup_timing field carrying cold-start telemetry: named startup phases and counters related to resuming and hydrating a session. This applies to hosted CCR sessions; it's absent elsewhere.

Why

This gives visibility into where time is spent during a hosted session's startup and resume process, which can help diagnose slow session starts.

Read from
Names in the bundlestartup_timing
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat "CCR" stands for and what specifically consumes this telemetry isn't stated.

See this entry in the whole of v2.1.265 →

Feedback