proomt

Search

Search posts, papers, and topics

All posts

.NETDaniel Roth11 min readintermediate

Build Agentic UI with the new Blazor AI components

Summary

The new experimental Blazor AI components provide building blocks for "Agentic UI," enabling developers to integrate AI agent interactions into Blazor applications. They offer components and a state model to render streamed agent output, tool calls, and shared application state.

  • Blazor AI components (`Microsoft.AspNetCore.Components.AI`) facilitate building UIs that interact with AI agents.
  • `ChatPage` provides a complete conversational UI, while `UIAgent` manages interaction state and maps agent responses to `ContentBlock` instances.
  • `ContentBlock` represents parts of an interaction (e.g., conversational content, tool calls) with observable state.
  • Integration with `AG-UI.NET SDK` allows connecting to remote agents via an open, event-based protocol.

This is important for .NET developers looking to build sophisticated AI-powered user interfaces that go beyond simple chat, enabling agents to collaborate with users on multi-step tasks.

7/10

Related reading

  1. Build Your Own AI Agent Harness in C#, the MafClaw Live Series

    The post walks .NET developers through using Microsoft Agent Framework's harness to turn a simple IChatClient into a fully‑featured C# AI agent, showing code for tool integration, file sandboxing, approval flows, and memory, then outlines further capabilities like skills and observability.

    .NETmicrosoft.com10 minHN2
  2. AG-UI Protocol now has a first-class .NET SDK

    The AG-UI protocol standardizes how AI agents communicate with user interfaces by streaming typed events. A new .NET SDK allows any .NET service to natively produce and consume these AG-UI events, enabling seamless cross-language interoperability between agents and UIs.

    .NETmicrosoft.com5 minrelease
  3. Workflow or agent? What building QAradar taught us

    Deezer built QAradar, a workflow‑driven Slack‑bot that lets developers discover and run the exact automated tests covering their feature. By pre‑generating a clean test catalog and keeping the LLM in a fixed four‑step workflow, they avoided the complexity and cost of a full‑blown agent while dramatically reducing knowledge silos and friction for QA and developers.

    Deezermedium.com6 min
  4. The case for a cloud native agent harness

    This article proposes a "cloud-native agent harness" architecture, exemplified by the open-source Mecatl, which decouples the agent loop from its environment. This enables running AI agents as distributed applications, offering durability, governed tool access, and multi-client support beyond a single desktop.

    CNCFcncf.io5 min