FrameworksOfficial

Microsoft previews Blazor AI components for controllable agentic UI

Experimental Blazor AI components map streamed agent interactions into UIAgent, ContentBlock and typed shared state for tools, approvals, plans and generated views.

Why it matters

The design shows generative UI entering a conventional application component model while the host retains control over layout, state commits and consequential actions.

A closer look

The components work with any IChatClient and can use the stable AG-UI .NET SDK for remote agents. Samples cover tool rendering, approvals, predictive-state accept or reject, and model-provided reasoning summaries.

Who this is for

.NET, Blazor and enterprise agent developers

Original sources

Revisions & corrections (1)

— New official source found outside the saved directory and independently read. The article date, preview status, architecture and limitations are explicit.

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.