Explore topics

Topic

AI Agent Orchestration

Orchestration is deciding which agent runs, when, and with what context. This topic collects the coordination patterns that come up in every multi-agent system — a router that classifies before it spends tokens, an orchestrator that delegates to typed sub-agents, parallel fan-out for independent work, and worker pipelines for dependent work. Each pattern is a running TypeScript implementation you can preview live and copy into your project. If you need coordination that survives restarts and waits on humans, continue to Durable AI Agents.

6 patterns6 featured

Orchestration vs. workflows

Orchestration answers who runs next inside a request: classify intent, fan out to specialists, merge results, and return. It lives in memory for the life of that turn — fast to reason about, easy to preview in a chat, and ideal when every step finishes before the response ends.

Workflows answer what survives failure. A durable workflow checkpoints between steps, retries only the failed branch, parks for human approval, and resumes after a deploy. Reach for orchestration when coordination is the problem; reach for Durable AI Agents when the work outlives a single request — cron digests, approval gates, and multi-minute pipelines.

Featured patterns

A curated starting point for this topic — open a live preview, then adapt the source.

6 curated

Related topics

Continue with adjacent topics that share the same building blocks.

Browse by category

Jump into the catalog filtered by category.

You’ve reached the end of AI Agent Orchestration.