event-deltas changedmanaged-agents/event-deltas
Nearest release: v2.1.308, published 2 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+3added
Lines−3removed
From line
31
where the diff opens
First seen
8 Oct 2026
this site's first read of the page
Recorded edits12to this page, all time
The whole hunk
from line 31, old and new numbered
/
from line 31
3131
3232When a previewed event starts, the stream emits an `event_start` carrying the upcoming event's type and `id`:
3333
34```json
34```text wrap
3535{
3636 "type": "event_start",
3737 "event": {
from line 43
4343
4444For `agent.message`, the start is followed by `event_delta` events carrying incremental text. Each delta names the event it extends in `event_id` and the content block it extends in `delta.index`:
4545
46```json
46```text wrap
4747{
4848 "type": "event_delta",
4949 "event_id": "sevt_01abc...",
from line 68
6868
6969## Accumulate and reconcile
7070
71Every SDK that supports event deltas includes an [accumulator helper](https://platform.claude.com/docs/en/managed-agents/event-deltas#sdk-accumulator-helpers) that handles the `index` bookkeeping for you. The manual pattern in this section works in every language when you need custom bookkeeping. Apply it to the generated event types.
71Every SDK that supports event deltas includes an [accumulator helper](https://platform.claude.com/docs/en/managed-agents/event-deltas#sdk-accumulator-helpers) that handles the `index` (csharp, go: `Index`) bookkeeping for you. The manual pattern in this section works in every language when you need custom bookkeeping. Apply it to the generated event types.
7272
7373In the manual pattern, hold preview text in a temporary map keyed by `(event_id, index)`, and treat the buffered event as the record. Reconcile the two for each model request.
7474
No line in this hunk matches that.