Microsoft Agent Framework for Go

Microsoft's open-source framework for building production-grade AI agents and multi-agent workflows in Go, with orchestration, observability, and Foundry integration.

Stars
★ 695
Last updated
today
License
MIT
Primary language
Go

At a glance

How it runs
Library / SDKFramework
Works with
Universal · cross-platformOpenAI API
Cost
Free software; you pay for model usage
Setup effort
Medium · a few setup steps
You'll need
GoAzure CLI (az login) for Foundry/Azure credentialsMicrosoft Foundry project endpoint or OpenAI API credentialsShell / CLINetwork accessLocal filesystemMCP Server
Typical use
Go teams building production multi-agent orchestration beyond a single prompt: sequential, concurrent, group collaboration, and custom routing
Not a fit if
  • Teams needing declarative agents, DevUI, AF Labs, or handoff orchestration, which are not yet implemented in the Go SDK
  • Development teams not using Go; .NET and Python implementations live in the upstream repository
  • Teams unwilling to accept public-preview status for production systems
Website
aka.ms/agent-framework ↗ set on GitHub
Maintenance
Commits in the last 30 dayslast commit 2026-11-22
Source review
82/100 · Good

What does this agent do, and when should you use it?

Microsoft Agent Framework for Go (microsoft/agent-framework-go) is the Go implementation of Microsoft Agent Framework, in public preview and evolving outside the upstream core alongside the .NET and Python implementations. It ships agent, provider, workflow, and middleware packages for building, orchestrating, and deploying AI agents and multi-agent workflows. The framework integrates with a broad ecosystem including Microsoft Foundry, Azure OpenAI, OpenAI, MCP, A2A, AG-UI, and the GitHub Copilot SDK. Workflows are graph-based, supporting sequential, concurrent, and group-collaboration patterns, conditional routing, subworkflows, checkpointing, streaming, human-in-the-loop, and time-travel. The Go SDK covers core agents, tools, middleware, workflows, observability, and interoperability, while declarative agents, DevUI, AF Labs, and handoff orchestration are not yet implemented.

It calls Foundry and OpenAI models through provider packages such as provider/foundryprovider and provider/openaiprovider, running agents via a.RunText(ctx, ...). The workflow package builds graph-based multi-agent orchestration with sequential, concurrent, and group-collaboration patterns, conditional routing, subworkflows, checkpointing, streaming, and human-in-the-loop control. agent/middleware.go provides request/response processing, OpenTelemetry, tool approval, and automatic tool calling. agent/skills, agent/textsearch, and agent/memory supply domain skill bases, automatic RAG retrieval with citations, and vector-backed chat memories. The vectordata package offers vector stores including Azure AI Search and an in-memory connector with hybrid search, and the embedding package generates provider-independent embeddings. Observability flows through provider/otelprovider and workflow/observability/opentelemetry for distributed tracing. Examples run from examples/01-get-started through examples/03-workflows and examples/05-end-to-end.

  1. Go teams building production multi-agent orchestration beyond a single prompt: sequential, concurrent, group collaboration, and custom routing
  2. Platform teams needing checkpointable, restartable, observable (OpenTelemetry) workflows with human-in-the-loop control
  3. Enterprise developers building project-backed Foundry agents or invoking existing server-side Foundry agents
  4. Knowledge applications that need automatic retrieval and citation of external knowledge (RAG) or session-backed vector memories
  5. Integrations requiring MCP servers, A2A, or AG-UI interoperability
  6. Teams needing vector search, hybrid search, and embedding generation infrastructure

Key setup facts

Pulled from the install and usage notes below. The project README has the current values.

Environment variables
FOUNDRY_PROJECT_ENDPOINT FOUNDRY_MODEL

How do you install or deploy this agent?

Install with go get:

go get github.com/microsoft/agent-framework-go

Before running samples, authenticate to Azure/Foundry (az login is recommended for development) and set the relevant environment variables.

How do you use this agent?

A minimal Foundry agent that writes a haiku:

package main

import (
	"cmp"
	"context"
	"fmt"
	"os"

	"github.com/Azure/azure-sdk-for-go/sdk/azidentity"
	"github.com/microsoft/agent-framework-go/provider/foundryprovider"
)

func main() {
	endpoint := os.Getenv("FOUNDRY_PROJECT_ENDPOINT")
	model := cmp.Or(os.Getenv("FOUNDRY_MODEL"), "gpt-4o-mini")

	token, err := azidentity.NewDefaultAzureCredential(nil)
	if err != nil {
		panic(err)
	}

	a := foundryprovider.NewAgent(endpoint, token, foundryprovider.ModelDeployment(model),
		foundryprovider.AgentConfig{
			Instructions: "You are a helpful assistant.",
		},
	)

	ctx := context.Background()
	fmt.Println(a.RunText(ctx, "Write a haiku about the Microsoft Agent Framework").Collect())
}

Set FOUNDRY_PROJECT_ENDPOINT (optionally FOUNDRY_MODEL) and authenticate with az login first. See examples/01-get-started, examples/03-workflows, and docs/agent-harness.md for more.

What are this agent's strengths and limitations?

Pros
  • Officially maintained by Microsoft with a broad ecosystem: Foundry, Azure OpenAI, OpenAI, MCP, A2A, AG-UI, and GitHub Copilot SDK, reducing lock-in to one provider
  • Graph-based workflows include checkpointing, restartability, streaming, human-in-the-loop, and time-travel patterns aimed at production
  • OpenTelemetry integration at both the agent/provider and workflow layers for distributed tracing and debugging
  • Complete retrieval and memory stack: agent/skills, agent/textsearch (RAG), agent/memory, vectordata, and embedding packages
Limitations
  • Public preview: declarative agents, DevUI, AF Labs, handoff orchestration, and Foundry-hosted deployment are not implemented in the Go SDK, which trails .NET
  • Using third-party servers, agents, or non-Azure direct models is at your own risk, with usage, costs, and compliance responsibility on you
  • Responsible AI mitigations (metaprompting, content filters) must be implemented by you in production
  • By default a feature-usage bitmask is appended only on approved Azure/Foundry HTTPS destinations; disable with AGENT_FRAMEWORK_FEATURE_MASK_DISABLED if unwanted

How does this agent compare with similar options?

The upstream microsoft/agent-framework repository hosts the .NET and Python implementations with broader product integrations and more complete features; the Go SDK is a public preview that currently evolves outside the upstream core, with closer alignment expected. A feature comparison is documented at docs/dotnet-go-sdk-feature-comparison.md.

Key facts side by side with the most closely related agents.

Agent Source review Form / cost Stars Updated Language Full support on
Microsoft Agent Framework for Go This agent 82 · Good Library / SDKFree + model costs ★ 695 today Go OpenAI API
Microsoft Agent Framework Hands-On Samples 54 · Major gaps Library / SDKFree + model costs ★ 397 5mo ago Jupyter Notebook —
Microsoft Agent Framework 70 · Some gaps Library / SDKFree + model costs ★ 15k 5d ago Python OpenAI API
AgentOS 64 · Some gaps Library / SDKFree + model costs ★ 691 1d ago TypeScript Claude Code · OpenAI API · Claude API

How does FollowAgents rate this agent?

FollowAgents source review · FARS-2.1
Good
82/ 100 5-point scale 4.1 / 5
Trust 21/29
Reliability 11/14
Adaptability 16/18
Convention 15/18
Effectiveness 12/13
Verifiability 7/8
Why each dimension lost points
Trust21 / 29 · 3.6/5

Framework itself ships no dangerous defaults: the telemetry doc states the feature mask is emitted only to allowlisted Azure hostnames, never third parties, with env-var opt-outs; the README assigns third-party risk explicitly to users and recommends managed identity for production. Least privilege is reasonable but no code-level permission audit is present in the sample (deducted). Tool-approval middleware is claimed, indicating a confirmation mechanism, but its source is not in the packet, so 2. Data-flow transparency is excellent: per-bit mask semantics, emission conditions, hostname allowlist, opt-outs. Sensitive data: docs claim the mask contains no user data and users are told to audit data flows, but no masking/encryption code evidence. Dependency security: pinned, well-known modules in go.mod, but no vulnerability-scan configuration shown. External effects require explicit env vars/credentials; no destructive defaults. Rollback: only workflow checkpointing is mentioned; no framework-level rollback documented — clear deduction. Attribution is clear: MIT, Microsoft copyright, MSRC reporting path.

Reliability11 / 14 · 3.9/5

Self-consistency is strong: README, telemetry doc, and verifyexamples behavior align, unimplemented features are explicitly flagged, no contradictions. Dependency availability: pinned reputable modules, but AG-UI uses a pseudo-version commit dependency (unstable provenance, deducted). Failure messaging: catalog and verify tools produce structured, explicit errors; README has an auth troubleshooting table; runtime error quality is not evidenced in the sample, so 2.

Adaptability16 / 18 · 4.4/5

Audience/scenarios well covered: a dedicated fit-check section plus production, orchestration, RAG, and memory scenarios. Capability boundaries are a highlight: unimplemented Go SDK features (handoff, declarative agents, AF Labs, DevUI, Foundry hosting) are enumerated alongside a .NET-Go parity doc. Trigger precision: the sampled SKILL.md files have clear descriptions and argument hints, but they are repo-internal tooling skills rather than the product's user-facing trigger surface, so 2. Environment fit is good: quickstart, env-var table, az login guidance, and a verifier tool target the Go/Azure environment.

Convention15 / 18 · 4.2/5

Information architecture is excellent: complete TOC, progressive example categories, links to concrete paths. Install notes are one usable line but lack version/release-channel guidance (deducted). Naming is consistent (provider/, agent/, workflow/), but public-preview status means API instability, so 2. Examples and FAQ are rich: progressive samples, troubleshooting tables, transparency FAQ. Known limitations are honestly listed. License is complete (MIT, Microsoft copyright). Versioning/changelog: no CHANGELOG and no version policy despite a v0.1.0 User-Agent — clear deduction. Maintenance responsibility is clear: CONTRIBUTING, SECURITY, SUPPORT policies and an MSRC vulnerability path.

Effectiveness12 / 13 · 4.6/5

Output usability is good: deterministic example verification and buffered structured JSON catalog output. Marginal value is high: no equivalent Go counterpart to MAF .NET/Python exists; the symbol catalog and feature-mask tooling are distinctive contributions. Cost/benefit: the dependency surface (many cloud SDKs) and learning cost are sizable for non-Azure users, hence a deduction.

Verifiability7 / 8 · 4.4/5

Claim traceability is strong: every README feature links to a concrete example or package; the telemetry doc links a pinned .NET registry commit. Cross-source corroboration: README and feature-usage-telemetry.md agree on telemetry behavior, but static review cannot execute checks and SKILL-referenced remote gh-aw content is not in the packet, so 2. Fact/inference separation is good: implemented vs. unimplemented, preview status, and an explicit note that declaration matches do not establish behavioral parity — evidence is honest.

Risks and how to mitigate them
  • The project is in public preview; APIs may change, so plan for churn in production use.
  • Rollback documentation is thin: workflows support checkpointing, but framework-level recovery paths need independent verification.
  • Feature-mask telemetry is on by default (Azure allowlisted hosts only); set AGENT_FRAMEWORK_FEATURE_MASK_DISABLED or USER_AGENT_DISABLED if no telemetry is desired.
  • Data flows and risks for third-party systems (OpenAI, MCP, A2A, etc.) are the user's responsibility; audit data boundaries and approval mechanisms yourself.
  • The go.mod dependency surface is large and includes a pseudo-version dependency (AG-UI); re-verify dependency provenance and vulnerability status for production.
Evidence confidence: Low Reviewed Nov 22, 2026 Reviewed revision 045c7be52783
See the full review method →
Maintain this project? Add the FARS badge to your README

The badge shows the current review score and verdict and links back to this page. It refreshes about once an hour after a re-review.

FARS

[![FARS review](https://followagents.com/badge/agent-framework-go.svg)](https://followagents.com/en/agents/agent-framework-go)
<a href="https://followagents.com/en/agents/agent-framework-go"><img src="https://followagents.com/badge/agent-framework-go.svg" alt="FARS review"></a>

FAQ

Can I use this in production?
The Go SDK is in public preview. Microsoft expects closer alignment with the broader MAF ecosystem as adoption grows; production use requires your own risk assessment and responsible AI mitigations.
What does it cost?
The framework itself is MIT-licensed and free, but calling Foundry, Azure OpenAI, or OpenAI models incurs API usage costs that you are responsible for.
What telemetry does it collect?
The repository does not configure a Microsoft telemetry exporter. OpenAI/Foundry adapters append a process-wide feature-usage bitmask only on approved Azure/Foundry HTTPS destinations; it records capabilities exercised, not prompts, arguments, or user data. Set AGENT_FRAMEWORK_FEATURE_MASK_DISABLED=true or AGENT_FRAMEWORK_USER_AGENT_DISABLED=true to opt out.
What features are missing from the Go SDK?
Declarative agents, DevUI, AF Labs, handoff orchestration, and Foundry-hosted deployment are not yet implemented; see docs/dotnet-go-sdk-feature-comparison.md for the .NET-to-Go gap.
Which model providers are supported?
The README explicitly lists Microsoft Foundry, Azure OpenAI, and OpenAI, plus MCP, A2A, AG-UI, and GitHub Copilot SDK ecosystem support, with more providers being added continuously.
Is Microsoft Agent Framework for Go open source?
Yes. The source code is on GitHub (microsoft/agent-framework-go) under the MIT licence.
Is Microsoft Agent Framework for Go safe to use?
FollowAgents' FARS review (Nov 22, 2026) scored Microsoft Agent Framework for Go 21/29 on trust and safety. None of the eight safety controls the review checks for was missing outright.
Is Microsoft Agent Framework for Go still maintained?
Yes. The latest commit on GitHub is from 2026-11-22, within the last 30 days.
Who makes Microsoft Agent Framework for Go?
Microsoft Agent Framework for Go is published by Microsoft. FollowAgents verified that the GitHub account microsoft belongs to Microsoft.
What is Microsoft Agent Framework for Go's official website?
The project's GitHub repository lists https://aka.ms/agent-framework as its website. That link is set by the repository owner; the source code itself is on GitHub (microsoft/agent-framework-go).
Was this page helpful?
View on GitHub ↗ Install ↓

Compare agents like this one

The same FARS review applied across the shortlist this agent qualifies for.

Related concepts