FrameworksOfficial

assistant-ui adds experimental queued steering and history recovery

October 15 updates add opt-in message queuing and repair history-loading races with live messages.

Why it matters

Editorial implication: stateful interfaces depend on ordering and tool-completion boundaries.

A closer look

Steering waits for the active request and client tools, then precedes ordinary follow-ups. Pre-dispatch failures remain retryable. Cancelled tool output no longer auto-sends.

Who this is for

Agent application developers

Original sources

Revisions & corrections (1)

— Distinct October 15 @assistant-ui/ai-sdk 0.0.13 immutable release, not October 13 generative-frame. Use version-specific canonical URL to avoid broad changelog collision.

Related events

Frameworks

assistant-ui's October 28 release tightens prompt review, tool-result ownership and configuration writes

assistant-ui released a coordinated package set on October 28. Generative Frame 0.0.9 fills the composer with widget and MCP App prompts for review before sending; assistant-stream 0.3.55 fixes stale model content surviving a later tool response and pending results moving when tool-call IDs are reused; the CLI also narrows configuration paths and plan-revision boundaries.

Frameworks

AI SDK 7.0.155 removes runtime checks already guaranteed by static types

Released October 27, AI SDK 7.0.155 stops revalidating message history against the ModelMessage schema in text and object generation and removes several shape checks covered by TypeScript, reducing a linear cost in long conversations and multi-step runs.