Agent design patterns
Agent design patterns describe how agents are arranged: Single-Agent Pattern, Multi-Agent Pattern, Planner-Executor Pattern, Supervisor Pattern, Router Pattern, Swarm Pattern, Hierarchical Agents and Blackboard Pattern.
In plain terms
A simple assistant may be one agent. A larger system may route requests, delegate work to specialists, share notes on a blackboard or arrange agents in manager-worker levels.
Why it matters
Architecture should match the work. Multiple agents add coordination cost, so patterns help you choose deliberately instead of adding complexity because it sounds advanced.
How it works
Single-Agent Pattern gives one agent the full job. Multi-Agent Pattern splits work among specialists. Planner-Executor Pattern separates planning from execution. Supervisor Pattern puts a manager over worker agents. Router Pattern sends requests to the right component. Swarm Pattern coordinates without a central controller. Hierarchical Agents use manager-worker levels. Blackboard Pattern lets agents collaborate through shared knowledge.
When you use it
Use patterns when the workflow has clear roles, branching, review needs or scale. Keep a single agent when the task is linear.
Common mistakes
- Starting with Multi-Agent Pattern before one agent works.
- Using Swarm Pattern where a simple Router Pattern is enough.
- No shared state contract in Blackboard Pattern.
Best practices
- Draw the pattern before coding.
- Evaluate each role separately.
- Prefer the simplest pattern that passes the evals.
Try it yourself
Design the same research workflow as Single-Agent, Planner-Executor and Supervisor Pattern, then pick the simplest one that meets the requirements.