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 ·

Turn-result wall-clock timing fields now gated to the matching user message

Turn-timing fields in the result event now only appear when they match the current turn's user message

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

In the final result event that Claude Code emits at the end of a turn, two wall-clock timing fields, request_sent_wall_ms and first_stream_post_wall_ms, are now only included when they belong to the same user message that the current turn is actually reporting on. The other send-echo timing fields are still always included as before.

Why

Previously these two timing fields could be attached to a result even when they came from a different user message than the one the result was about, which could make timing data misleading. Restricting them to the matching message keeps the reported timings accurate.

Read from
Names in the bundlerequest_sent_wall_msfirst_stream_post_wall_ms
What the documentation says

See this entry in the whole of v2.1.265 →

Feedback