Orchestration
From one agent to many changes the problem from prompts to systems design. Five patterns, two protocols and what breaks first.
8 Oct 2026 · 6 min read
Moving from one agent to many changes the problem from prompts to systems design. In 2026 a handful of orchestration patterns dominate production, and the best starting point is usually the simplest.
The supervisor is the 2026 production default: Claude Code subagents, LangGraph's supervisor pattern and the OpenAI Agents SDK handoffs all converge on it. It scales because adding a specialist means registering it with the supervisor and defining its scope and permissions, not rewiring everything.
MCP, the Model Context Protocol, standardizes how agents reach tools and data, so a connector is written once and reused. A2A, the Agent-to-Agent protocol, standardizes how agents talk to each other: discovering capabilities, handing work off in a structured way and acknowledging it. Together they cover tool access and peer collaboration, and the orchestration layer supervises both.
Start with a supervisor and two or three specialists with narrow tools. Add approval gates for irreversible actions and budgets per task. Instrument before you scale. Only then add fan-out for parallel work, and consider swarms when there is a clear need and an evaluation to prove it. Common frameworks include LangGraph, CrewAI, Microsoft Agent Framework, Google ADK, the OpenAI Agents SDK and the Claude Agent SDK, with durable engines such as Temporal for long-running work.

Tell us about one process. We'll show you how an agent could handle it, and what to measure to know it's working.