Skip to main content

​
Browser demo

Try ECP (Execution Control Protocol) in the browser with the Graph Editor — a reference app that runs Fluent workflows with on-device or local models. Live demo: https://demo.executioncontrolprotocol.io/ Source and local setup: github.com/executioncontrolprotocol/browser-demo

​
Try the hosted demo

  1. Open the live demo in Chrome (recommended).
  2. Complete the first-run provider modal.
  3. Chat with the assistant and use the panels for Fluent, JSON, run, and validation.
Default path: Chrome AI + the nano harness — on-device, no local daemon. The canvas Inputs / Outputs nodes come from the workflow contract (accepts / returns). They are projections of that schema, not dummy steps. See Fluent API. Chat can also drive a discover-then-finish loop: when the assistant offers a probe, confirm to inspect live structure, pick options in follow-up messages, then complete and run the workflow.

​
Ollama with ecp up

For local models and the coding (Fluent/TS) path:
  1. Install and start Ollama; pull a model (for example qwen2.5-coder:1.5b).
  2. Install the ECP CLI, then:
ecp up starts a loopback bridge and opens the hosted demo with pairing query params. Hosted HTTPS pages need Chromium (Chrome/Edge) for Private Network Access to the loopback bridge.
For flags and daemon details, see CLI: ecp up.

​
Run from source

Clone browser-demo, then:
Open the URL Vite prints (default http://localhost:5173). No core monorepo clone or .env is required for the default Chrome AI path. For linking unpublished packages (pnpm run link:ecp, pnpm run dev:linked), see the browser-demo README.

​
Providers and settings

Chrome AI vs Ollama, harness pairing, and where secrets belong are covered in Demo providers and configuration.

​
Next steps