Multi-Agent Wiki

Patterns Overview

Index of core multi-agent interaction patterns

The patterns below are not mutually exclusive — they compose. A production-grade coding agent might use Supervisor + Parallel Fan-out + Blackboard + Generator-Critic + Human-in-the-loop + MCP, all at once.

#PatternCategoryOne-liner
1Supervisor / ManagerControlA primary agent plans, routes, and synthesizes; specialists execute subtasks.
2Agents-as-toolsControlSpecialists are exposed as callable tools; the host keeps conversation control.
3Handoff / RouterControlThe current agent transfers control to another, which takes over the conversation.
4Sequential PipelineInformationTasks pass through agents in a fixed order; each step's output is the next step's input.
5Parallel Fan-out / GatherInformationSplit a task across many agents in parallel; an aggregator merges results.
6Hierarchical DecompositionControlMulti-level manager-worker tiers; upper tiers decompose, lower tiers execute, recursively if needed.
7Graph / State Machine / WorkflowControlDefine the flow with an explicit graph or state machine, not by letting the LLM improvise.
8Group Chat / MeetingInformationMultiple agents share one thread; a moderator or selector picks the next speaker.
9Nested Chat / Inner TeamInformationAn agent runs an internal multi-agent sub-conversation before replying outward.
10Debate / JudgeDecisionMultiple agents take opposing positions, then a judge or vote picks the result.
11Generator-CriticDecisionOne agent produces; another critiques, verifies, scores, or proposes edits.
12Refinement LoopDecisionGenerate → evaluate → revise, until an exit condition or budget is met.
13Role-playing / SOPEnvironmentAgents play PM, architect, dev, QA roles bound by a documented SOP.
14Blackboard / Shared MemoryInformationAgents collaborate indirectly via shared state, knowledge base, task board, or workspace.
15Event Bus / Pub-SubInformationAgents communicate asynchronously through events, topics, or queues — not direct calls.
16Market / Auction / Contract NetDecisionTasks and resources are allocated via bidding, pricing, or contract-net protocol.
17Peer-to-peer / SwarmControlNo fixed center; agents self-organize via direct messaging, shared environment, or dynamic handoff.
18Mixture-of-AgentsDecisionLayered ensemble — each layer reads multiple outputs from the previous and improves them.
19Human-in-the-loopEnvironmentA human is a special agent for approval, correction, routing, interruption, or final decision.
20Protocol-mediated NetworkProtocolConnect tools, agents, clients, and platforms via MCP, A2A, ACP, Agent Client Protocol.
21Clarification-at-edgeDecisionInsert a clarification step at agent-agent handoff boundaries or before uncertain actions.
22Coordinator / DispatcherControlDispatcher distributes requests to agents, workflows, or tools and owns task state, retry, timeout, routing.
23Voting / EnsembleDecisionIndependent candidates from multiple agents; a vote, score, or verifier picks the final answer.
24Composite PatternCompositionReal systems combine pipeline + parallel + handoff + critic + HITL + blackboard + protocol layers.
25Workspace / Sandbox IsolationEnvironmentEach agent runs in its own workspace, git worktree, container, or sandbox to avoid concurrent corruption.
26Stigmergy / Environment-mediatedEnvironmentAgents leave traces in the environment (issues, todos, diffs, test results); others react to them.
27Coalition / Federation / HolonicOrganizationAgents form temporary coalitions, federations, or holons — governance, membership, autonomy boundaries.
28Social SimulationSimulationSimulate a population, organization, or society with long-term memory, relationships, emergent behavior.
29MARL / CTDELearningMulti-Agent Reinforcement Learning; centralized training, decentralized execution.