AG-UI 1.0 lands a .NET SDK: build an agent UI once, run it anywhere

A frozen schema and MIT NuGet packages pull AG-UI into Microsoft's Agent Framework, as Oracle wires it into Agent Spec and Google counters with A2UI v0.9.

Nowline OCT 1 2:00 PM banner

Top AI stories from the last hour

Top AI stories from the last hour

Copy markdown

  • AG-UI 1.0: one contract between any agent and any frontend

    The spec froze to a stable 1.0 JSON schema covering token streaming, typed front- and back-end tool calls, shared state with conflict resolution, human-in-the-loop interrupts (pause, approve, edit, retry) and generative UI. Wire a backend to a UI once instead of rebuilding per framework — LangChain, CrewAI, Google ADK, AWS Strands, Mastra and Pydantic AI already speak it.

  • A first-class .NET SDK, and Microsoft Agent Framework moves onto it

    CopilotKit and Microsoft shipped five MIT-licensed NuGet packages (AGUI.Abstractions, Formatting, Protobuf, Client, Server) at v1.0.0 on Sept 25, aligned to the frozen schema. Microsoft Agent Framework dropped its in-house AG-UI code to depend on them, so on .NET 4.7.2+ you can expose or consume AG-UI agents through Microsoft.Extensions.AI — just rename AddAGUI() to AddAGUIServer().

  • Oracle folds AG-UI into its Agent Spec

    Oracle's Open Agent Specification now interoperates with AG-UI: define an agent once, pick a runtime, and connect to any AG-UI-ready frontend without rebuilding the interface per stack. It's another big-vendor signal that the agent-to-frontend contract is settling.

  • Google counters with A2UI v0.9

    Google published its own generative-UI spec, A2UI v0.9, now wired into Gemini Enterprise — a competing answer to the same 'stop shipping the same form four times' problem. Choosing an agent-UI standard today means weighing AG-UI's frozen 1.0 against Google's still-moving A2UI.

  • Why it lands on your stack

    The agent-UI layer is narrowing to a few protocols (AG-UI and A2UI on top of A2A and MCP). Build against a frozen 1.0 and your streaming, tool-call and approval plumbing survives a framework swap; guess wrong and it's a rewrite. An afternoon prototyping against AG-UI now is cheap insurance before your next agent frontend.