Skip to main content
KAOP Workflow Orchestrator is the Komodor Agentic Operation Platform (KAOP) catalog agent that does no specialist work itself: it decides which agents should, delegates to them, and combines what comes back. It runs a declarative workflow over your fleet, and it is also the account’s executor for a module workflow’s orchestrated steps. It delegates over agent-to-agent invocation through the control plane, so every specialist call is authorized and recorded like any other run rather than becoming an unobserved side channel.

​
Running a workflow

A workflow is steps that fan out to several specialists at once, run in order, or loop until the work is done. The contained-failure behaviour is the one to design around: a workflow finishing does not mean every step succeeded, so read the steps rather than the outcome.

​
Executing an orchestrated step

A module workflow’s steps come in two kinds, and the orchestrator handles one of them: Either way the outcome is written back onto the step run, which is the only place a caller learns what happened.
An account has one step executor: whichever agent holds the step-orchestrator role is the one every orchestrated step dispatches to. Deploying a second does not give you two — it gives you a question about which one holds the role.
You do not usually invoke this path directly. It is what makes a module’s workflow steps run, and it matters when you are reading a workflow’s traces or working out why a step routed the way it did.

​
Next steps

Orchestration

Steps, agent binding, and the orchestrator-and-specialist pattern.

Agent catalog

Every deployable agent, and what each one is for.

Modules & workflows

The packaged workflows these steps belong to.

Runs & evidence

Reading a delegated run and the spans that link it.