Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

SDK result messages can now report a breakdown of time before the first model request

Successful SDK results gain timing fields that break down the delay before the first model request, under the same conditions as startup timing

You'll notice No documentation found Improvements
JSON All of v2.1.285
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SDKArea: what it touches
ImprovementsKind: in v2.1.285,
ImprovementsSection of the release
What

The SDK is the toolkit for running Claude Code from your own programs. When a run finishes successfully, it sends back a result message. That message used to carry only time_to_request_ms and some frame timings. It can now also carry a more detailed breakdown:

  • time_to_request_phases_ms, time split by phase before the first request to the model
  • process_turn_index, which turn this is within the process
  • time_to_request_cpu_ms, processor time spent
  • time_to_request_loop_lag_ms, time lost to delays in Claude Code's internal processing
  • time_to_request_major_faults, a count of slow memory accesses that had to go to disk
  • turn_start_phases_ms, time split by phase at the start of the turn
  • turn_start_control_requests_ms, time spent on control requests at the start of the turn
  • api_error, a typed error field

These fields appear in sessions run with CLAUDE_CODE_REMOTE, and on setups that set CLAUDE_CODE_EMIT_STARTUP_TIMING.

Why

If Claude Code feels slow before it starts answering, these fields show where that time goes.

Read from
Names in the bundletime_to_request_ms

See this entry in the whole of v2.1.285 →

Feedback