// glossary
Multi-Agent System plain-English.
Operator-grade definition. Plain words, plus where the term shows up in real work.
What is a Multi-Agent System?
A multi-agent system is a software system in which two or more AI agents act with their own scope and tools, coordinated to produce a shared outcome. Each agent owns a slice of the work — a role, a lane, a queue — and the orchestration layer keeps them from stepping on each other.
The simplest version: one operator dispatches a small fleet of agents (Claude, Cursor, Codex, Copilot) on independent tasks against a shared codebase, with CI and required checks acting as the reviewer. Each agent works in its own worktree, opens its own pull requests, and lands only on green checks. Coordination is structural, not chatty.
More complex versions: agents with different roles (planner, builder, verifier, security reviewer) that hand off work via typed contracts. The challenge is the same: prevent silent state corruption, give the operator a kill switch, and design the failure modes so the fleet degrades gracefully when one agent goes rogue.
The honest take: most production multi-agent systems are simpler than the marketing implies. A fleet of identical agents working in isolated lanes, gated by CI, is doing 80% of what the buzzword promises — and is the version that actually survives Friday deploys.
Related questions
Is one agent calling another a multi-agent system?
Technically yes, but the term usually refers to systems where multiple agents work in parallel with their own scope, not just a single agent that delegates a sub-task.
Why use multiple agents instead of one?
Parallelism without context-switching, role specialization, and isolation between failure domains. The cost is orchestration overhead — only worth paying once the workload justifies it.
How is a multi-agent system different from a microservice architecture?
Microservices are deterministic processes coordinated by RPC; multi-agent systems are non-deterministic actors coordinated by language plus protocol. Some patterns transfer; failure modes do not.
Related work
Need someone to actually run this in production? book a call.