PhyseaWiki How AI actually works physea.ai →

Workflows & orchestration

What are the main AI orchestration patterns?

Microsoft's catalog of multi-agent orchestration patterns names five: sequential (a pipeline), concurrent (parallel perspectives), group chat (a shared thread, including the maker-checker loop), handoff (dynamic delegation), and magentic (an open-ended plan built as the work proceeds).

Last updated 2026-07-25 · Physea Labs

Microsoft’s architecture guide names five patterns for coordinating multiple agents, chosen by matching the pattern to the shape of the coordination problem rather than picking a favorite.[1]

Multi-agent orchestration Sequential a pipeline Concurrent run at once Group chat shared thread Handoff dynamic transfer Magentic plan as you go
Each pattern trades away something different: sequential trades speed, concurrent trades a fixed order, group chat trades cost, handoff trades a single point of control, magentic trades predictability.
  • Sequential chains agents in a predefined, linear order. Each agent processes the previous one’s output, forming a pipeline of specialized transformations — a good fit when the steps themselves are fixed, like a document moving through drafting, review, and formatting.[1]
  • Concurrent runs several agents on the same task at once, each contributing an independent perspective. Useful when you want diverse analysis or a form of voting, not a division of labor.[1]
  • Group chat puts multiple agents into one shared conversation thread, with a chat manager deciding who responds next. A specific, more structured version of this is the maker-checker loop: one agent proposes, another evaluates against defined criteria, and the proposal cycles back with feedback until it is approved or the orchestration hits a maximum number of iterations.[1]
  • Handoff lets agents dynamically delegate: each agent can assess a task and either handle it or transfer it to a more appropriate specialist based on what it finds, the way a support ticket gets escalated to whoever actually knows the answer.[1]
  • Magentic is for open-ended problems with no predetermined plan. A manager agent builds and refines a task ledger as the work proceeds, developing goals and subgoals on the fly rather than following a route decided in advance — the pattern for “we don’t know the steps yet,” not just “we don’t know the answer yet.”[1]

These describe how several agents split one job between them. A related but distinct taxonomy, from Anthropic’s guidance on structuring a single model’s calls, covers prompt chaining, routing, parallelization, orchestrator-workers, and the evaluator-optimizer loop — see workflows vs agents for that list.[2] The two overlap in spirit: chaining resembles sequential, routing resembles handoff. But Microsoft’s set assumes multiple independent agents, where Anthropic’s assumes one model filling in different wiring.

References

  1. AI Agent Orchestration Patterns — Microsoft Azure
  2. Building Effective Agents — Anthropic