assistant-ui makes aborts, rate limits, persistence failures and composer origins observable
assistant-ui's October 22 package set distinguishes rate limits, validation failures, server errors, aborts, incomplete runs and persistence failures in Cloud telemetry, while attaching origins to composer text changes.
Why it matters
If a generative interface collapses “no reply,” “storage failed” and “the user stopped” into one empty state, product and audit systems cannot decide whether to recover, retry, explain or stop. Draft recovery likewise depends on why the text changed.
A closer look
assistant-cloud 0.2.8 maps HTTP 429, 400/422 and 5xx to rate_limited, validation_failed and server_error. Stops before the first token report aborted, and output-free completion reports incomplete. Failed history appends or updates are no longer skipped or reported completed; they become persistence_error. React/Vue 0.15.31/0.0.6 also tag composer.textChange as user, recall, send, return, reset or external, and disable unarchive controls when an adapter cannot restore a thread.
Who this is for
Frontend and platform teams building multi-turn agent UI, draft recovery, run monitoring and failure audit
Original sources
- assistant-ui official releases and pull requests ↗github.com
- Failed and stopped run outcomes ↗github.com
- Persistence-error reporting ↗github.com
- Unarchive capability guard ↗github.com
- Composer text-change origin events ↗github.com
Revisions & corrections (1)
— The October 22 official package releases combine distinct but related runtime observability and recovery-boundary changes; linked merged PRs provide scope and known omissions.