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.282 ·

SDK results can carry an internal breakdown of message intake timing

The SDK result format gains an optional internal field timing each step between a message arriving and being queued

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

Unclear It is not clear whether Claude Code currently fills in this field.

What

The result format used by the SDK (the kit for driving Claude Code from other programs) has a new optional field, frame_intake_phases_ms. It splits the time between a message from the host program arriving and it being queued for Claude into steps: before_read, dedup, flag_settle, receive_hook, attachments, admission_wait, admit_check and other. The format marks the field as internal.

Why

The breakdown helps show where time goes when a message sent to Claude Code is slow to start being handled, for example on a slow first turn in an SDK or remote session. Because it is marked internal, it is not meant to be relied on.

Read from
Names in the bundleframe_intake_phases_ms
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 doubtIt is not clear whether Claude Code currently fills in this field.

See this entry in the whole of v2.1.282 →

Feedback