Orcho makes AI work accountable

Read first

AI agents are workers. Orcho is the local-first control plane and delivery protocol around them: profiles define the work shape, gates decide whether it can continue, and evidence keeps readiness inspectable.

intentprofilepipelinegatesevidence

Start quickstart5-minute story

live CLI firstmono-run firstdeep reference later

orcho run —output liveoperator view

Orcho Run  20260629_1427  profile=feature
Task  Add validation to the login endpoint

Pipeline
⟳² (▶ plan [Claude] → · validate_plan [Codex]) → · implement [Claude]
  → ⟳² (· review_changes [Codex] → · repair_changes [Claude])
  → · final_acceptance [Codex]

[PLAN] accepted implementation contract
[IMPLEMENT] edited api/auth.py and tests
[REVIEW_CHANGES] verdict=REJECTED
blocker  missing negative-path test
next     correction follow-up

Primary perception

The terminal stream shows phase progress, agent output, findings, and next action while the run is alive.

Afterwards

orcho status and orcho evidence help inspect the persisted record.

Artifacts

output.log, events.jsonl, plan.md, review.json, diff.patch

01Read the 5-minute storyOne run from task intent to review, repair, final gate, and evidence.02Watch the live runThe CLI stream is the first operator UX.03Read a real runPipeline DSL, gates, findings, usage, and evidence.04Open the mapMove from light entry to advanced and expert layers.

Semantic plane

A profile tells Orcho what kind of work this is

task intentprofilephasesgatesevidence

Do not read Orcho as “run many agents.” Read it as “choose the operating shape for a task.” The same request can be a light mono-run, a gated implementation run, a review-only run, or a participant-set workflow. The profile makes that choice explicit before the lifecycle starts.

Understand profile semantics

Choose your level

Read from light entry to expert control

01Light entryUnderstand Orcho, run one mono task, watch live output, and read the result.02Advanced operatorOperate feature runs, inspect evidence, handle rejects, resume, and control through MCP.03Expert builderShape profiles, gates, workspaces, prompt composition, runtime adapters, and low-level contracts.

Choose your sub-domain

Orcho has separate operating planes

Run controlLifecycle, phase gates, follow-ups, resume, and delivery decisions.Profiles and gatesWorkflow depth, readiness policy, false-ready delivery, and verification receipts.Evidence and trustStatus, evidence bundles, receipts, artifacts, events, diffs, and final acceptance.Workspaces and participantsRun state, generated worktrees, mono-run first, participant-set topology, and cross-project delivery.Cross-project modeOne feature intent, project aliases, per-project handoffs, contract check, and one system gate.Worker runtimesClaude, Codex, Gemini, phase routing, runtime readiness, and adapter boundaries.Prompt engineRole/task/format composition, protected contracts, project overrides, and utility-lab primitives.Skill registryPortable capability packages, trust policy, subtask routing, and skill-use evidence.MCP and referenceTyped run control for clients plus CLI, artifact, and event contracts.