Asim Aslam
c7657f73f4
* test(harness): read agent plan from the scoped store
The store-scoping change moved an agent's plan from the default table
key agent/{name}/plan to its own table (database "agent", table {name},
key "plan"). The plan-delegate harness tests still read the old key and
failed with 'not found'; read through store.Scope(mem, "agent", name)
like the agent does.
* docs: orient agents-first across README, landing, and docs overview
Lead with agents (then services and flows), surface MCP + A2A as the
interop story, and frame agents as services. Landing hero and feature
grid reordered agents-first with an A2A gateway card.
* v6: module path go-micro.dev/v6, TLS secure by default, NewService
Cut v6. Three breaking changes, bundled so the major bump is paid once:
- Module path go-micro.dev/v5 -> go-micro.dev/v6 across all imports + go.mod.
- TLS verification on by default (was off). MICRO_TLS_SECURE removed;
MICRO_TLS_INSECURE=true opts out for self-signed/dev.
- micro.NewService(name, opts...) is the canonical service constructor,
symmetric with NewAgent/NewFlow; micro.New kept as a deprecated alias;
the old name-less NewService(opts...) removed. Generators emit NewService.
Also ports the JWT auth token provider in-module (go-micro.dev/v6/auth/jwt/token
on golang-jwt/jwt/v5), dropping the v5-pinned github.com/micro/plugins/v5/auth/jwt
and the deprecated dgrijalva/jwt-go.
Docs/README/landing updated to v6 and @latest; v5->v6 migration guide added;
CHANGELOG cut as [6.0.0]. Blog posts left at their historical versions.
---------
Co-authored-by: Claude <noreply@anthropic.com>
2.6 KiB
layout
| layout |
|---|
| default |
Docs
Documentation for the Go Micro framework.
Overview
Go Micro is a framework for building agents and services in Go. Build an agent and it gets a model, memory, and tools, manages your services, and is reachable over MCP and A2A. Write services and they register, discover each other, and every endpoint is automatically an AI-callable tool. Orchestrate the deterministic parts with flows. Agents, services, and flows come from the same primitives — because an agent is a distributed system, and building one is building a service.
It's built on a pluggable architecture of Go interfaces: service discovery, client/server RPC, pub/sub, plus auth, caching, and storage. Sane defaults out of the box, everything swappable.
Learn More
To get started follow the getting started guide. Otherwise continue to read the docs for more information about the framework.
Contents
- Getting Started
- MCP & AI Agents - Turn services into AI-callable tools with the Model Context Protocol
- CLI & Gateway Guide - Development vs Production modes
- Quick Start
- Architecture
- Configuration
- Registry
- Broker
- Client/Server
- Transport
- Store
- Plugins
- Examples
Development & Deployment
- micro run - Local development with hot reload, API gateway, and agent playground
- micro build & deploy - Build binaries and deploy to production
- micro server - Optional production web dashboard with auth
AI & Agents
- Building AI-Native Services - End-to-end tutorial for MCP-enabled services
- MCP Security Guide - Auth, scopes, rate limiting, and audit logging
- Tool Description Best Practices - Writing docs that make agents effective
- Agent Integration Patterns - Multi-agent workflows and architectures