title: "Microsoft ships .NET SDK for AG-UI protocol" slug: "microsoft-ships-net-sdk-for-ag-ui-protocol" published: "2026-10-05" beat: "Tools" tags: ["Tools"] creator: "Agentry Newsroom" editor: "Susanne Sperling, Editor — Human in the Loop" tools: ["Claude (Anthropic)", "Perplexity Sonar"] creativeWorkStatus: "verified" dateReviewed: "2026-10-05" aiActArticle50: "compliant" humanView: "https://agentry.news/tools/microsoft-ships-net-sdk-for-ag-ui-protocol" agentView: "https://agentry.news/agent/microsoft-ships-net-sdk-for-ag-ui-protocol"
Microsoft released a first-class .NET SDK for the AG-UI protocol on September 25, 2026, and refactored its Agent Framework to depend on shared AGUI packages instead of maintaining its own implementati
Drafted by an AI agent. Verified by Susanne Sperling, Editor — Human in the Loop. AI policy.
Microsoft released a first-class .NET SDK for the AG-UI protocol on September 25, 2026, and refactored its Agent Framework to depend on shared AGUI packages instead of maintaining its own implementation Microsoft .NET Blog.
The AG-UI .NET SDK ships as five NuGet packages: protocol types, wire formatters, protobuf support, an HTTP client, and a framework-agnostic server adapter built on Microsoft.Extensions.AI Microsoft .NET Blog. These packages are now available on NuGet for developers to integrate into their agent projects.
The Microsoft Agent Framework previously included its own implementation of the AG-UI protocol, but now depends on the shared AGUI.* packages from NuGet instead Microsoft .NET Blog. The framework retains its ASP.NET Core integration, which allows developers to turn an agent into an HTTP endpoint.
This move is a developer tooling shift that reduces duplication in the .NET agent stack. By extracting AG-UI support into shared packages, Microsoft is signaling that the protocol is now a platform standard rather than a framework-specific detail. Developers building agents in .NET can now use the same AG-UI packages whether they're using Agent Framework, building custom implementations, or integrating with third-party tools.
The refactor also reduces maintenance burden on Microsoft's Agent Framework team, allowing them to focus on agent execution, orchestration, and resilience rather than protocol transport layers. This is typical of mature platform evolution: once a protocol proves itself in production, implementations migrate to shared libraries.
The SDK is production-ready and available now via NuGet. Developers can immediately adopt the AGUI.* packages in new projects or migrate existing Agent Framework implementations to the shared packages. The HTTP client enables agents to communicate with AG-UI-compatible front ends; the server adapter allows .NET services to expose agent capabilities as HTTP endpoints.
The protocol types and protobuf support packages ensure that .NET developers can serialize and deserialize AG-UI messages without reimplementing the spec. This is especially important for interoperability: agents built with different frameworks but speaking the same AG-UI dialect can compose and communicate without custom marshaling code.
Microsoft's decision to split protocol support out of Agent Framework suggests the company expects AG-UI to become a cross-platform standard. Other runtime vendors (Python, Go, JavaScript) would likely benefit from similar extractions, making it easier for mixed-language agent teams to operate.