Every term in this hub.
This hub collects the orchestration terms in the Prefactor glossary. The patterns group covers how an individual agent thinks in steps: ReAct, plan-and-execute, planning loops, and the agentic loop itself. These are the concepts you meet first, because every multi-agent system is built out of single agents that use them.
The multi-agent group is where the coordination problems live: orchestrator and supervisor agents, sub-agents, handoffs, and swarms. The routing group covers the decision of which agent or model handles a request at all. And the memory group covers what persists between steps and sessions, because an agent that forgets everything between turns pushes the coordination burden onto everything around it.
A fair warning about this vocabulary: it is the least standardised in the glossary. What one framework calls a supervisor another calls an orchestrator, and the definitions here note those collisions where they matter rather than pretending one vendor's usage won.
Terms are grouped below from the inside out: reasoning patterns first, then multi-agent coordination, routing, memory and state, and finally the infrastructure pieces such as queues and middleware. Each entry links to its full definition.
Reasoning patterns & loops
Multi-agent coordination
Routing
Memory & state
Infrastructure
More agent orchestration & workflow terms
Common questions.
What is agent orchestration?
Agent orchestration is getting more than one step, and often more than one agent, to produce a coherent outcome: decomposing goals, routing sub-tasks, and merging results.
What is the difference between an orchestrator and a supervisor agent?
Usage varies by framework, which this vocabulary honestly reflects. Broadly, an orchestrator coordinates tasks across agents; a supervisor also monitors and can override them. The individual entries note the collisions where they matter.