orca-cli
We need to translate the given text from English to Traditional Chinese. The instruction says to preserve product names, protocol names, URLs, numbers, and technical terms. The name "orca-cli" is to be preserved if it appears in the source text, but we should not include it unless it appears. The source text includes "orca-cli" as part of the list of phrases. So we keep "orca-cli" as is. Also "Orca" is a product name, so keep as "Orca". "CLI" is technical term, keep as "CLI". "worktrees", "folder contexts", "terminals", "repos", "automations", "worktree comments", "browser", "Orca app", "cardStatus", "codex/claude", "terminal", "full handoff", "handover", "agent" - these are technical terms or product names, so we should preserve them in English or translate? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." So
npx skills add https://github.com/stablyai/orca --skill orca-cliOrca 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_COMMANDenvironment 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, useorca-dev. - Otherwise, on Linux outside an Orca-managed terminal, use
orca-ide. Never run bareorcathere — 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.