Or Orcho Install the public alpha

CLI

The CLI is the execution core.

Orcho starts from a CLI run engine. It can be used interactively in a developer terminal, but the same run model is designed for headless automation: explicit status, artifacts, metrics, evidence and resumable state.

AVAILABLE Route status
Run lifecycle MCP surface
run / cli gated
plan accepted
validate_plan accepted
implement evidence open
review_changes findings open
repair_changes queued
final_acceptance awaiting signoff

TTY

Interactive when a human is driving.

The CLI can show phase progress, gate state, summaries and next actions in a terminal workflow without forcing the operator into a separate app.

Headless

Structured enough for CI and automation.

The same engine writes durable status and artifacts instead of depending on terminal scrollback. That makes CI, scripts and external clients consumers of the run record, not parsers of prose.

Surfaces

MCP exists; TUI and web are operator surfaces.

MCP can already control and inspect runs programmatically. The TUI and web panel should be presented as in-development operator surfaces on top of the same CLI-backed run model.

  • CLI: execution core, interactive TTY and headless run mode.
  • MCP: available programmatic control surface.
  • TUI and web panel: in development / coming soon operator views.