Orca CLI

Operate Orca-managed worktrees, folder contexts, terminals

by stablyai · MIT license · ★ 84,481 on GitHub

Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the `orca` CLI. Use when the user says "$orca-cli", "Orca worktree", "child…

---
name: orca-cli
description: >-
  Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts,
  skill sharing, worktree comments, and Orca's embedded browser through the `orca` CLI. Use
  when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a
  worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another
  agent", "Orca browser", "orca artifacts", or "share skills". Prefer it over raw git
  worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only
  when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
---

# Orca CLI

This discovery stub loads the version-matched guide from the Orca executable used for this session.

## Resolve the CLI for this session

Overview

This discovery stub loads the version-matched guide from the Orca executable used for this session.

Manual install (npx, ZIP)

Claude Codenpx skills add stablyai/orca --skill orca-cli -g -a claude-code

Claude Code (degit)npx degit stablyai/orca/skills/orca-cli#main ~/.claude/skills/orca-cli

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.3 KB

Read SKILL.md here

stablyai/main1 file shown

SKILL.md2.3 KB

Browse every file on GitHub↗

SKILL.md

Show the full text48 lines

orca-cli/SKILL.md48 lines · 2.3 KB

PreviewCode

Outline

RawView on GitHub

Orca CLI

This discovery stub loads the version-matched guide from the Orca executable used for this session.

Resolve the CLI for this session

Choose the executable once and reuse it for every later command:

If the ORCA_CLI_COMMAND environment variable is set, use its value. Orca exports this for managed WSL sessions.
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 orca there — outside Orca's terminals it normally resolves to the GNOME Orca screen reader (/usr/bin/orca) and starts speech on the user's machine.
Otherwise, use orca.

Below, ORCA is a placeholder for the executable you resolved. Substitute it before running anything; do not create a shell variable or run ORCA literally. This works the same way in POSIX shells, PowerShell, and cmd.exe.

If the selected executable cannot run, report its exact error and stop. Do not fall through to another executable, which could silently target a different Orca build.

Load the version-matched guide before running Orca commands

ORCA skills get orca-cli

Prefer --json. Use the selected executable's --help for commands or flags the guide does not cover. If a command reports that Orca is not running, start it with ORCA open --json and retry. If it fails with runtime_access_denied, your sandbox blocked the connection: re-run it with escalated permissions, and do not run ORCA open or restart Orca. If skills get is unknown, explain that updating Orca restores the guide; use --help for read-only discovery and do not guess unsupported commands.

1	---
2	name: orca-cli
3	description: >-
4	Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts,
5	skill sharing, worktree comments, and Orca's embedded browser through the `orca` CLI. Use
6	when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a
7	worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another
8	agent", "Orca browser", "orca artifacts", or "share skills". Prefer it over raw git
9	worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only
10	when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
11	---
12
13	# Orca CLI
14
15	This discovery stub loads the version-matched guide from the Orca executable used for this session.
16
17	## Resolve the CLI for this session
18
19	Choose the executable once and reuse it for every later command:
20
21	- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this
22	for managed WSL sessions.
23	- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`.
24	- Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare
25	`orca` there — outside Orca's terminals it normally resolves to the
26	GNOME Orca screen reader (`/usr/bin/orca`) and starts speech on the user's machine.
27	- Otherwise, use `orca`.
28
29	Below, `ORCA` is a placeholder for the executable you resolved. Substitute it before
30	running anything; do not create a shell variable or run `ORCA` literally. This works the
31	same way in POSIX shells, PowerShell, and cmd.exe.
32
33	If the selected executable cannot run, report its exact error and stop. Do not fall through
34	to another executable, which could silently target a different Orca build.
35
36	## Load the version-matched guide before running Orca commands
37
38	```text
39	ORCA skills get orca-cli
40	```
41
42	Prefer `--json`. Use the selected executable's `--help` for commands or flags the guide does
43	not cover. If a command reports that Orca is not running, start it with `ORCA open --json`
44	and retry. If it fails with `runtime_access_denied`, your sandbox blocked the connection:
45	re-run it with escalated permissions, and do not run `ORCA open` or restart Orca. If
46	`skills get` is unknown, explain that updating Orca restores the guide; use `--help` for
47	read-only discovery and do not guess unsupported commands.
48