A book by Dayna Blackwell

Running Go Agents in Production

Identity, governance, and cost for agents at scale

Every call an agent makes asks five questions. This book builds the platform that answers them.

Run Go agents for a company: many people, teams, and agents on one platform, every call saying who it acts for, and rules, not the model, deciding what an agent may do.

It picks up where the first book ends, with an agent that works, and builds what it takes to run agents for other people.

In progress · about 50% complete

The first book
The cover of Running Go Agents in Production: a small blue gopher with a clipboard stands at a lit control desk with a lever and green gauges, while a stone android kneels beside it with an open hand, under a vaulted hall of cables and screens.

The project

What it builds

The first book ends with one agent shipped. This one builds the platform around it: a service people sign in to, a credential on every call that names the person, the team, the agent, and the run, and a gateway that every agent call passes through before it reaches a service.

On that platform you add more agents, agents that call other agents, and tenants that can’t see each other, then limit what each one can reach and spend. Last, you change it safely: a model or a prompt changes only after a release gate says it may, and one trace follows a call through every part.

One call that leaves an agent passes five questions in order, each with the part of the platform that answers it: who is acting (the credential), is it allowed (the gateway), what does it cost (quotas and the ledger), does it happen once (the service), and what happened (the record). A kill switch can cut the route anywhere. One call that leaves an agent passes five questions in order, each with the part of the platform that answers it: who is acting (the credential), is it allowed (the gateway), what does it cost (quotas and the ledger), does it happen once (the service), and what happened (the record). A kill switch can cut the route anywhere. One call that leaves an agent passes five questions in order, each with the part of the platform that answers it: who is acting (the credential), is it allowed (the gateway), what does it cost (quotas and the ledger), does it happen once (the service), and what happened (the record). A kill switch can cut the route anywhere. One call that leaves an agent passes five questions in order, each with the part of the platform that answers it: who is acting (the credential), is it allowed (the gateway), what does it cost (quotas and the ledger), does it happen once (the service), and what happened (the record). A kill switch can cut the route anywhere. One call that leaves an agent passes five questions in order, each with the part of the platform that answers it: who is acting (the credential), is it allowed (the gateway), what does it cost (quotas and the ledger), does it happen once (the service), and what happened (the record). A kill switch can cut the route anywhere.
Five questions asked of every call an agent makes. The book is organized around them.

Table of contents

Four parts, one platform

The titles so far. The book is in progress, and chapters can change before it is out.

Opening

The call path

Part 1

Who is acting

  1. Who is acting, for whom, in which tenant

  2. Sign-in and sessions

  3. Delegated access to other services

  4. MCP servers as resource servers

Part 2

Governing what agents do

  1. The gateway

  2. The tool supply chain

  3. Keeping the model out of the decision

  4. Human approval at scale

  5. Audit and the kill switch

Part 3

Running many agents

  1. Agents calling agents

  2. Tenant isolation

  3. Scaling out

  4. Cost, quotas, and the model gateway

  5. State and migrations

Part 4

Changing it safely

  1. Evals and model changes as a release gate

  2. Following one call across the platform

  3. Incidents

  4. Data: retention, privacy, and deletion

Capstone Is it ready to launch?

Status

In progress

About 50% complete

Chapters 1 to 17 are drafted. Chapter 18, the capstone, and the appendices are next.

The book is being written and has no release date or store page yet. It follows Building AI Agents in Go, which you can buy now and which covers everything this book builds on.

The Production section of this site already covers some of its topics, such as agent identity, agent gateways, and approval.