Chapter 9. Agent Orchestration Patterns
Everything in this book so far has been about working well with a single agent. You’ve learned to engineer its context (Chapter 3), to write specs it can execute (Chapter 6), and to stay in the loop at the right moments (Chapter 2).
This chapter is about what happens when one agent is not enough. Real work often outgrows a single context window, a single line of execution, or a single level of intelligence. When that happens, you stop talking to one agent and start designing how several agents work together. That design problem is called orchestration.
Orchestration is a set of patterns, each with a cost and a payoff, and you pick one based on the job in front of you. This chapter gives you those patterns and, just as important, the judgment to know when not to reach for them.
This is not a chapter for AI engineers whose job is building agent products. I will not cover agent frameworks, model serving, or how to design a multiagent system as software you ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access