assistant-ui react-ag-ui 0.1.6 fixes event ownership after snapshot head movement and settles disconnected answers as incomplete
assistant-ui released @assistant-ui/react-ag-ui 0.1.6 on November 11. Later text, tool calls, results, and subagent output now route to the assistant message named by the AG-UI event even after a message snapshot moves the current head to a later answer. An answer cut off by disconnect settles as incomplete. A paired fix keeps an answer running when a later snapshot adds a tool call to the current head.
Why it matters
A streamed generative-UI history can interleave snapshot replay, appended tools, subagent output, and network disconnects. If a frontend writes to the current head rather than the message named by the event, content lands on the wrong answer. If a truncated stream never settles, loading, retry, and audit state become misleading.
A closer look
Version 0.1.6 contains two scoped fixes: route later output by the event's named assistant message after snapshot head movement and mark a disconnect-truncated answer incomplete; and avoid incorrectly ending an answer when a later snapshot adds a tool call to the current head.
Who this is for
Frontend and agent-platform teams using assistant-ui with AG-UI snapshot replay, tools, subagents, or disconnect recovery.
Original sources
Revisions & corrections (1)
— The immutable assistant-ui release directly documents two state-machine fixes governing AG-UI event ownership, disconnect settlement, and snapshot-added tool calls.