AWS recommends starting with the simplest architecture that fits the task: use a fixed workflow when the steps are known, and reserve runtime-directed coordination for work that may uncover new subtasks as it runs. Its decision framework distinguishes a direct model call, a single agent with tools, and deterministic or autonomous multi-agent workflows. For coding agents, Stanford HAI reported that communication had almost no impact in the CooperBench tasks it summarized.
Fixed workflows and runtime-directed coordination
AWS groups multi-agent patterns by who controls the next step. In a deterministic workflow, the path is defined in advance. In runtime-directed coordination, an agent or planner chooses what happens next as the work unfolds. These are AWS’s categories and guidance, not a universal standard.
| Pattern | Control flow | Example fit described by AWS | Practical trade-off |
| Sequential pipeline | Fixed stages pass outputs from one to the next | Document processing or shift-handoff summaries | Predictable to test and debug, but an early error can carry through later stages. |
| Conditional workflow | Predefined branches handle outcomes such as pass, failure, or retry | A process that routes a failure to a retry path | Set a retry limit and escalate when it is reached. |
| Conditional router | Classifies an input and sends it to one specialist path | Intent routing or quality triage | Only the selected branch runs. |
| Parallel fan-out/fan-in | Independent tasks run concurrently; a later stage combines the results | Work that can be split into independent analyses | The slowest worker can determine elapsed time, and the aggregator still has to reconcile outputs. |
| Plan-based orchestration | A planner assigns tasks and dependencies at runtime | Work where subtasks emerge during analysis | Flexibility adds cost, latency, and debugging complexity. |
| Peer handoff | An agent transfers control and task state to another agent | A specialist escalation or domain change | AWS recommends passing validated state, supporting evidence, and unresolved questions rather than relying on a conversational summary alone. |
| Conversation-driven coordination | Agents share a conversation and take turns | Open-ended collaboration | State is implicit in the conversation history, which participants can see. |
| Debate or consensus | Independent results are reconciled by a majority, judge, or escalation | High-stakes, low-volume decisions | AWS describes this as its most expensive pattern and warns that debate can add latency without improving accuracy on perceptual tasks. |
A Spanish-language presentation by LIDR - Desarrollo potenciado por IA also surveys single-agent, tool-using, router, multi-agent, and autonomous patterns. Its speaker describes combining patterns with techniques such as planning and human review.
Choose the simplest architecture that fits the task
AWS’s decision path starts with a practical question: does the task require actions beyond generating text? If not, a direct model call may be enough. If it does, ask whether the solution path is known. For a known path, use one agent with tools unless the work genuinely needs distinct expertise; in that case, a deterministic multi-agent workflow may fit. When the path is unknown, runtime-directed coordination is worth considering when the task requires exploration or has significant side effects. Otherwise, a single agent may suffice.
Add runtime-directed coordination when the work needs to discover its own next steps, not merely because several tasks can run at once.
More processes do not automatically mean a better architecture. AWS recommends checking whether one agent can handle the phases by switching tools before splitting the work. One Reddit user, u/Far_Reindeer8428, reported that three agents working in one repository became difficult to coordinate until each had a separate worktree and review step. Other commenters preferred a persistent main session with selective delegation to avoid cold starts and fragmented context; these are individual working preferences, not a measured comparison.
Bound coordination risks
AWS identifies five failure patterns to watch for:
- The “god agent”: one agent handles many unrelated tools, making tool choices and failures harder to manage. AWS suggests bounded specialist roles and proposes five tools or fewer as a limit.
- Unbounded iteration: retries can consume tokens and compound coordination failures. Set iteration and token ceilings, with an automatic stop when the budget is reached.
- Natural-language contracts: free-text handoffs can turn a tentative observation into a definitive claim or action. AWS recommends typed, schema-validated handoffs.
- Premature multi-agent design: splitting work adds coordination overhead when one agent can switch tools and handle the phases. Test that simpler arrangement first.
- Unguarded customer contact: an unreviewed action can affect customers or physical systems. AWS proposes guardrails, schema validation, business rules, human approval, and then execution.
AWS’s reliability illustration shows why long dependent chains need deliberate failure handling: if each step is 95% reliable, a strictly sequential chain without retries comes to 59.9% after 10 steps and 35.8% after 20. Those figures are illustrative calculations, not measurements of a deployed system.
After choosing an architecture, teams still need to decide how to evaluate its outputs. NeoTeo’s guide to evaluating AI agents beyond their final response covers that adjacent question.
Keep manufacturing control deterministic
For manufacturing, AWS recommends using agents to observe, analyze, and recommend while keeping control in deterministic PLC, SCADA, and MES systems. It advises checking recommendations against the current operational-technology state and matching approval to the action’s scope before a permitted command reaches control systems.
Latency, physical safety, edge-resident data, and shift changes shape this design. AWS recommends budgeting latency at the 99th percentile and providing a deterministic fallback under one second. It also proposes keeping time-sensitive signal processing at the edge while cloud systems support cross-shift and cross-plant analysis. For memory, its suggested cycle is to start a shift with crew and target context, retain working memory during that shift, and pass open issues and recommendations to the next crew.
What CooperBench says about coding-agent teamwork
In its June 1, 2026 summary of CooperBench, Stanford HAI described more than 650 conflict-prone software-engineering tasks in Python, TypeScript, Go, and Rust. The agents could edit code, run local commands, and message each other. Stanford HAI reported that enabling communication had almost no impact on results in those tasks.
The summary described agents ignoring merge-conflict warnings and failing to follow through on promised work. Those observations concern the benchmark’s coding tasks; they do not establish how every multi-agent architecture performs.