orca-cli

# Orca CLI Use `orca` when Orca's running editor/runtime is the source of truth. On Linux, use `orca-ide` wherever this file says `orca`. **Dev builds (`pnpm dev`):** after `pnpm build:cli`, the dev CLI is exposed as `orca-dev` (the global shim points at this checkout's wrapper + out/cli). Inside a dev Orca's terminals use `orca-dev emulator ...` (or `./config/scripts/orca-dev.mjs emulator ...` for worktree-local invocation that does not depend on the /usr/local/bin symlink). Plain `orca` targets any installed production Orca. The app's own agent preambles use `orca-dev` automatically in dev mode. Use plain shell tools when Orca state does not matter. ## Start Here ```bash command -v orca || command -v orca-ide orca status --json orca worktree ps --json orca terminal list --json ``` If Orca is not running, start it: ```bash orca open --json orca status --json ``` Prefer `--json` for agent-driven calls. If the CLI is missing, say so explicitly instead of inspecting source files first. ## Worktrees An Orca worktree/workspace is Orca's tracked view of a repo checkout, its metadata, terminals, browser tabs, and UI state. Common commands: ```bash orca repo list --json orca repo show --repo id:<repoId> --json orca repo add --path /abs/repo --json orca repo set-base-ref --repo id:<repoId> --ref origin/main --json orca repo search-refs --repo id:<repoId> --query main --limit 10 --json orca worktree list --repo id:<repoId> --json orca worktree ps --json orca worktree curre...