Agent orchestration

The layer that decides which agent or step runs next, in what order and with what shared state, when a task needs more than one agent.

Agent orchestration coordinates multiple agents or steps toward one outcome. One pattern is manager-led delegation, where a parent agent decides at run time which specialist agent to call, treating each one like a tool. The other is an explicit orchestrator, a graph of states and edges defined ahead of time, where the control flow is fixed and only the content varies.

Enterprises that automate a real process, not just a single question, need orchestration to stay predictable and reviewable. A loan review or a claims workflow already has a defined sequence of steps in the business, and the automation should mirror that sequence rather than leave the order of operations to a single model's judgement on every run.

A request comes in, an intake agent classifies it, a document agent extracts the relevant fields, and a policy agent checks them against the rules, each step handing off to the next in a fixed order.

In Dynamiq, both patterns are available: attach an agent as a tool of another agent for delegation, with call limits and a setting that lets a specialist's answer pass straight back as the final one, or use the Graph Orchestrator to define states, edges and conditions explicitly. Every step, in either pattern, appears in the run's trace.

See an agent on your own workflow.

Bring a process and its documents. Our engineers will show you how Dynamiq runs it, in your environment or ours.