What it does. This file is a discovery stub, not the usage guide. The full, version-matched Orca CLI reference is served by the
orca
binary itself — kept out of this file on purpose so it can never drift from the binary that will actually run your commands.
Engage Orca whenever its running editor/runtime is the source of truth: Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and the browser embedded inside the Orca app. Triggers include "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "full handoff" / "handover" / "give this to another agent", and "control the browser inside Orca". Use plain shell tools when Orca state does not matter.
Highlights
- If the
ORCA_CLI_COMMAND
environment variable is set, use its value. Orca exports this
- Otherwise, in a dev checkout whose session exposes
ORCA_DEV_REPO_ROOT
, use orca-dev
.
- Otherwise, on Linux outside an Orca-managed terminal, use
orca-ide
. Never run bare
- Otherwise, use
orca
.
When to use it. Drive the public orca CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations and artifacts.
Install
npx skills add stablyai/orca --skill orca-cli
Or copy the skill folder manually:
git clone https://github.com/stablyai/orca.git
cp -r orca/skills/orca-cli/ ~/.claude/skills/orca-cli
Source: stablyai/orca — 59,988 stars, MIT, last pushed 2026-09-02.
