Siddharth Ganesan b98ef9b70a Persist subagent lane lifecycle blocks from the span handler ...

Lane-scoped span events route to the span handler, which only recorded trace
side effects — no subagent start block was ever persisted (verified: a
seven-agent run stored 104 blocks with zero starts). Grouping then fell back
to keying lane content by agent NAME, so a respawned agent of the same type
merged invisibly into the first one's card until it resolved. The handler now
persists the start block (spanId-keyed and deduped, carrying the display
name) and stamps endedAt on close, giving every invocation its own card.

2026-08-14 13:18:36 -07:00

..

desktop

feat(desktop): coordinate clicks, caret insertion, and drag for the browser agent

2026-08-13 15:25:32 -07:00

docs

feat(v2): complete and align the v2 API surface (#6643)

2026-08-12 15:04:24 -07:00

pii

fix(pii): mask offloaded large payloads chunk-by-chunk instead of aborting at 16MB (#5810)

2026-07-21 18:03:14 -04:00

realtime

feat(workflows): new workflow block card, progress indicator, colors, dsl for natural language preview, retry configs (#6458)

2026-08-10 19:21:32 -07:00

sim

Persist subagent lane lifecycle blocks from the span handler

2026-08-14 13:18:36 -07:00