back
loading skill details...
Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and the browser embedded inside…
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 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:
don't have the plugin yet? install it then click "run inline in claude" again.