Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchBlazor’s new AI components let developers build agent experiences around a conversation: stream progress, render tool requests, pause for approval and keep structured application state beside the chat. They are experimental throughout .NET 11, however, and provide UI building blocks—not an agent that automatically designs or controls an application.
What “agentic UI” adds to a Blazor app
A chat transcript shows what a person and an AI model said. An agentic interface can also show what the agent is doing and give the person a way to guide consequential steps. In a travel-planning workspace, for example, a conversation could sit alongside a structured itinerary that updates as the agent works. A progress indicator could expose an activity, while a proposed booking action could be presented for the app to handle or the user to approve.
Those are patterns the components can support, not a promise that every sample or app includes every feature. Microsoft describes the new experimental components as “building blocks for these experiences, which we call Agentic UI,” in Daniel Roth’s September 28, 2026 .NET Blog announcement.
Components for conversation, content and activity
ChatPage provides a complete chat shell combining AgentBoundary, MessageList and MessageInput. Developers can instead use or customize those lower-level pieces. UIAgent wraps an app-provided IChatClient and turns streaming updates into observable content blocks. The component set also includes rich-text and tool rendering, client-side UIActionBlock handling, and ActivityContentBlock handlers for mapping provider- or app-specific progress updates into UI activity. Microsoft documents the components and their status in What’s new in ASP.NET Core in .NET 11.
#1 Best Overall
Can an agent update the page, not just reply in chat?
Yes, if the application defines the UI and state that should change. UIAgent<TState> provides typed, observable application state separately from conversational content. That lets a workspace display an app-defined object—such as a draft plan—alongside messages. The components do not invent the state model or decide how it should appear; the developer defines the shape and renders it.
With an AG-UI integration, server-side agent code can map selected tool results to STATE_SNAPSHOT or STATE_DELTA events. The Blazor client can deserialize those updates and set the agent’s state. This separates the conversation from the structured state the application chooses to share.
How tool calls and approvals fit together
Frontend tools run in the Blazor client, where they can work with UI state or local preferences, or request input from the person using the app. When an agent asks for a frontend tool, UIAgent represents the request as a UIActionBlock for the application to handle. It is not silently executed by the remote agent server.
That distinction gives the app a place to show what action is being requested and, where appropriate, ask for confirmation. The application remains responsible for the action’s behavior and approval experience; the presence of these components alone is not a security guarantee. Backend tools, by contrast, execute on the agent server.
Rank #3
Do you need AG-UI?
No—not for basic chat. The Blazor AI components accept any IChatClient from Microsoft.Extensions.AI, a set of provider-neutral abstractions for AI services and common middleware patterns. Microsoft describes facilities including tool invocation, telemetry and caching in its Microsoft.Extensions.AI libraries documentation.
Microsoft recommends AG-UI when a remote client and server need to exchange richer agent events, such as frontend tool declarations, backend tool events, approval interrupts, shared-state updates or AG-UI conversation identifiers. The AGUI.Client package supplies AGUIChatClient, which streams AG-UI events as ChatResponseUpdate values. Microsoft describes the protocol’s capabilities, including real-time streaming, session context, approvals, state synchronization and custom UI rendering, in its AG-UI integration with Agent Framework guidance.
Rank #4
How the pieces can fit an app architecture
Microsoft names Microsoft.Extensions.AI, the AG-UI .NET SDK, Microsoft Agent Framework (MAF), ASP.NET Core, Microsoft Foundry and Aspire as building blocks for agentic applications. They are ecosystem options, not a required bundle. The useful choice depends on what the app needs: a chat client abstraction, a remote-agent event connection, an agent framework, web hosting, model services or application orchestration.
The new UI components sit in the Blazor application layer. Developers still provide the AI client, decide which tools and content the app exposes, implement action and approval UX, and map application state. The documentation does not establish comparative performance benchmarks or production outcomes for these new components.
Free tools Windows power users keep installed
One-click scans. No signup required.
What is new compared with Blazor AI chat?
Blazor already has AI chat patterns. Microsoft’s AI app template documentation describes an Interactive Server sample using Microsoft.Extensions.AI packages, an IChatClient, an embedding generator and a chat UI that supports response citations. The new components extend the interaction surface toward tool handling, activity, approvals and separately modeled shared UI state; they do not make ordinary chat obsolete.
Preview status and version caveat
The components are experimental and prerelease throughout the .NET 11 release line, according to Microsoft’s ASP.NET Core release notes. For .NET 11 RC1, the documented package version is 0.1.0-preview.1.26459.102. Treat the APIs and setup as preview material: check the current release notes before copying a version-specific package command or relying on an API in a production application.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
