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.
Why it matters
Generative-UI reliability extends beyond rendering. Users need a chance to see interface prompts before an agent sends them, history adapters must return every tool result to the correct call, and an installer must not write model-produced configuration outside the project. These fixes cover human review, causal message history and the local filesystem boundary.
A closer look
`generative-frame@0.0.9` puts widget and MCP App prompts into the composer before transmission. `assistant-stream@0.3.55` discards stale model content when a newer tool response omits it and keeps pending results attached to their original calls when an ID is reused. `setup-agent@0.0.7` rejects decisions scoped to a superseded setup or plan revision, binds model-key redemption to the requesting CLI, and refuses symlinks or resolved configuration paths outside the project. The 0.0.127 main package carries the path fix, limits its WebMCP skill guidance to the Chrome 149–156 origin trial and testing flag, adds audited cloud setup flows, and includes accessibility, scrolling and visible-text streaming fixes.
Who this is for
Frontend and agent-platform teams using assistant-ui, MCP Apps, Generative Frame, history adapters, cloud threads and automated setup CLIs
Original sources
- assistant-ui official immutable package releases ↗github.com
- assistant-stream 0.3.55 history and tool-result fixes ↗github.com
- Generative Frame 0.0.9 review-before-send fix ↗github.com
- setup-agent 0.0.7 revision, key and filesystem-boundary fixes ↗github.com
Revisions & corrections (1)
— Backfill a verified recent immutable release that closes user-review, message-causality and local configuration boundaries relevant to generated interfaces.