Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.259 ·

SDK turn results now include user_message_uuids for consumed prompts

Turn telemetry now tracks up to 64 user message uuids, including prompts queued but not yet started.

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

Turn telemetry now tracks up to 64 user message uuids, including prompts queued but not yet started.

Assistant message/result frames (complete, partial-first-frame, and stream-event variants) and the result schema gain a new user_message_uuids array listing every user message uuid consumed by or merged into a turn, in order, capped at 64 entries, including uuids for prompts that were queued but not yet started during the turn. This lets SDK consumers bind a reply to any of the sends it answers, not just the first.

A new helper (Jc) tracks the up-to-64 recently-seen user message UUIDs and attaches them as user_message_uuid/user_message_uuids to result and error telemetry via sendEcho, errorVariantFields(), and related call sites, fully wired into the query loop's telemetry emission.

Read from
Names in the bundleuser_message_uuids
What the documentation says

See this entry in the whole of v2.1.259 →

Feedback