assistant-ui's November 13 releases extend durable AG-UI across history ownership, concurrent threads, and cross-worker cancellation

assistant-ui released @assistant-ui/react-ag-ui 0.1.10 and Python assistant-stream 0.0.38 on November 13. Frontend fixes cover persistence of snapshot-selected answers, joined-step ordering, unique tool-call ownership, and streamless resume. The server adds compare-and-set thread claims, per-run context, SSE keepalive, and cross-worker cancellation.

Why it matters

Long generative-UI tasks cross browser disconnects, load balancers, workers, and history reconstruction. The recovered interface remains coherent only when message ownership, tool approval, and run ownership survive those boundaries without losing answers, duplicating calls, or letting an older run overwrite a newer thread.

A closer look

react-ag-ui 0.1.10 replays reasoning, assistant records, and tool results in step arrival order while preserving signed reasoning and redacted-block ownership. resumeRun follows an in-flight stream before starting again. Python adds atomic thread claims, per-run adapters and async contexts, optional SSE pings, and shared-store cross-worker cancel. The project reports 1,135 react-ag-ui tests passing and 443 DurableAGUI tests passing with Postgres 16 and Redis 7 enabled.

Who this is for

Frontend and agent-platform teams using assistant-ui, AG-UI, Pydantic AI, durable threads, multi-worker deployment, or tool-approval recovery.

Original sources

• assistant-ui immutable react-ag-ui and Python assistant-stream releases ↗github.com
• Atomic durable-thread claim implementation and tests ↗github.com
• DurableAGUI cross-worker implementation and tests ↗github.com
• assistant-stream 0.0.38 immutable release ↗github.com