Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.277 ·

New detailed timing telemetry for message enqueue and turn start

New telemetry breaks down how long messages take to enqueue and turns take to start, using new frame-timing data

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaTelemetrywhat it touches
KindInternal Changesin v2.1.277,
Group of 2 Under the hood

New telemetry breaks down how long messages take to enqueue and turns take to start, using new frame-timing data

What

When a message is delivered, Claude Code now records frameTiming (a received and an enqueued wall-clock timestamp) on the command.

  • The cli_user_message_enqueued telemetry event gains new fields: parse_to_enqueue_ms, dedup_ms, flag_settle_ms, receive_hook_ms, and, when attachments are present, attachments_ms, attachment_count, and inlined_images, plus parked_ms when a park timestamp was recorded.
  • A new telemetry event, cli_turn_started, is emitted when a turn is dispatched, including the turn's uuid, the batch size, and enqueue_to_start_ms (the time from when the turn was enqueued to when it actually started), whenever frame timing info is available.

Why

This gives a more detailed breakdown of where time goes between a message arriving and a turn actually starting, which helps diagnose latency in message handling.

See this entry in the whole of v2.1.277 →