CLI

This page is a compact map. Full command reference will be generated from the current CLI before public release.

Common commands

orcho --help
orcho workspace init ~/www/my-workspace
orcho run --project ~/www/my-workspace/my-project --task "..." --output live
orcho cross --projects api:/repo/api web:/repo/web --task "..." --profile feature --output live
orcho status
orcho evidence --format md

Output modes

orcho run --project ./my-project --task "..." --output summary
orcho run --project ./my-project --task "..." --output live
orcho run --project ./my-project --task "..." --output debug

• summary: compact progress and outcome.
• live: summary plus live agent transcript; best first UX.
• debug: live output plus deeper traces for diagnosis.

--stream-output is an alias for --output live.

Cross-project command

Use orcho cross when one feature intent spans more than one project:

orcho cross \
  --projects api:/repo/api web:/repo/web \
  --task "Align the user payload contract across api and web." \
  --profile feature \
  --workspace /repo/workspace-orchestrator \
  --output live

The command starts a cross run with named project aliases. Orcho plans at the cross level, writes per-project handoffs, runs project sub-pipelines, then checks the coordinated result with cross-level gates when the selected profile enables them.

Read Cross-project mode before making it your first multi-project delivery path.

Non-interactive CI mode

Use --no-interactive when a run must not prompt on stdin:

orcho run \
  --project ./my-project \
  --task-file .orcho/tasks/add-login-validation.md \
  --profile feature \
  --no-interactive \
  --output summary

For fresh non-interactive runs, pass a concrete --profile unless the auto-detect advisor policy is already configured and trusted. Without a terminal picker, Orcho should not guess the run shape silently.

--no-interactive applies to both orcho run and orcho cross. It suppresses interactive prompts and lets configured policy handle dirty-checkout intake, eligible handoff retries, verification blocks, and delivery decisions.

Read CI autopilot before wiring this into scheduled jobs.

First principle

The CLI has two jobs. During the run, live output is the primary operator UX. After the run, the directory artifacts are the source of truth.