Microsoft Agent Framework for Go: agents as one binary

Most AI agent code today ships as a Python project with a dependency tree nobody wants to own in production. Microsoft's Agent Framework for Go hit public preview on July 10, and the interesting part isn't the framework — it's the runtime. A Go agent compiles to a single static binary you drop on a server. For a small team maintaining automations, that difference is most of the operational cost.

What actually happened

Microsoft Agent Framework started in October 2025 as the merge of AutoGen and Semantic Kernel, and reached 1.0 for .NET and Python. The Go implementation is now in public preview via go get github.com/microsoft/agent-framework-go.

What's in the box: providers for Microsoft Foundry, Azure OpenAI and OpenAI-compatible endpoints, Anthropic, Gemini, and A2A. Tool calling, Model Context Protocol support, middleware, context providers, and approval gates. Multi-agent workflows with routing, checkpoints, streaming, and human review. OpenTelemetry tracing for agent runs.

Two honest caveats. It's a preview and Microsoft says the APIs may evolve with feedback, so this isn't the week to port a working system onto it. And The New Stack notes the Go implementation is currently developing outside the core upstream codebase, which means feature parity with Python and .NET lags.

Why a Go agent runtime matters for your business

Skip the language war. The operational math is what matters.

A Python agent in production means a virtualenv, a pinned dependency set, a base image, and a person who understands why it broke after an unrelated upgrade. A Go agent means one compiled binary with no runtime to install. If you run automations on a VPS, in a container, or on a box in the back office, that's the difference between a service you maintain and a service you forget about — in the good way.

The MCP support is the part to actually care about, and it's not Go-specific. Agents that talk to your systems through MCP are agents whose tools survive a framework change. We've argued this repeatedly — build on the standard, not the vendor — and it's why a new framework landing with MCP on day one is a reasonable signal rather than another lock-in surface.

Our read: don't migrate anything today. Do note that "agents must be Python" stopped being true, and factor that into the next automation you scope for deployment rather than for a demo.

Sources: Microsoft for Go Developers blog, The New Stack.