Go Micro

Go Micro is an agent harness and service framework for Go.

Community: questions, ideas, or just want to build alongside us? Join the Discord.

A harness is the runtime around an agent: the tools it can call, the memory it keeps, the guardrails that bound it, the workflows that trigger it, the services it depends on, and the protocols other agents use to reach it.

Go Micro gives you the harness as Go code. Build an agent and it gets a model, memory, tools, planning, delegation, guardrails, and service discovery; it is reachable over MCP and A2A. Write services and every endpoint becomes an AI-callable tool. Orchestrate the deterministic parts with durable flows. Agents, services, and flows share one runtime because an agent is a distributed system, and building one is building a service.

Sponsors

     

Want to support Go Micro and see your logo here? Become a sponsor — reach out on Discord.

Commercial Support

Running Go Micro in production, or building on it and want help? Paid support, consulting, training, and retainers are available directly from the maintainer — and they're what keep the project maintained. See Support for the tiers, or open a request.

Contents

• Quick Start
  • First agent on-ramp
• Why an Agent Harness
• Writing Services
• Building Agents — Plan & Delegate, Pluggable, Paid tools (x402), A2A
• Features
• CLI
• Autonomous improvement loop
• Multi-Service Projects
• Data Model
• AI Providers
• Examples
• Commercial Support
• Docs

Quick Start

Install the CLI:

# Binary (no Go required)
curl -fsSL https://go-micro.dev/install.sh | sh

# Or with Go
go install go-micro.dev/v6/cmd/micro@latest

If install or PATH checks fail, use the install troubleshooting guide before scaffolding your first service.

Fastest start — no API key

Scaffold a service, run it, call it:

micro new helloworld
cd helloworld
micro run

Then in another terminal:

curl -X POST http://localhost:8080/api/helloworld/Helloworld.Call \
  -H 'Content-Type: application/json' -d '{"name":"World"}'

This install → scaffold → run → call path is covered by no-secret CI harnesses. To verify just the local installer and first-run CLI boundaries without network access or provider keys, use:

make install-smoke

To run the broader local contract (including the 0→hero services → agents → workflows path, chat/inspect CLI boundaries, and deploy dry-run), use:

make harness

First agent on-ramp

After install and the first micro new/micro run smoke check, take the walkable agent path in this order:

1. Install troubleshooting — verify the binary installer or go install, PATH, micro --version, and the no-secret smoke path before agent work.
2. micro agent demo — print the provider-free