Skip to main content
ECP (Execution Control Protocol) is the deterministic delegation layer an agent uses when work should be repeatable, governed, and repairable. You reason about an approach once, capture it as a workflow file, and run it under policies instead of re-prompting a model every time. MCP standardizes how models call tools. ECP standardizes how an agent delegates a graph of those tools: which steps run, in what order, under which plugins and policies, with a journal you can inspect and rerun.

​
Determinism ladder

  1. Search the installed capabilities (ecp search, ecp describe).
  2. Author a single *.ecp.ts workflow file.
  3. Validate (ecp validate --json) until the graph and bindings are sound.
  4. Run (ecp run --json). On failure, read the error code and the journal.
  5. Repair the file and ecp runs rerun --from <step>.
The CLI is the primary surface. A model should learn flags from ecp --help. MCP (ecp mcp serve) exposes the same host as tools. The visual App (ecp app) is the same host in a graph.

​
Install

The field-test is 0.50.0 on latest (not 1.0). Contributors who are changing packages can build from source. Then:

Quickstart

Install the CLI, add the skill, and run the echo workflow.

The agent loop

Author, validate, run, read the journal, rerun.

Workflow files

Fluent TypeScript that compiles to a portable JSON graph.

CLI reference

Generated from oclif manifests.

​
What you operate

​
Next steps