orca CLI manages agents, sessions, skills, vaults, files, kits, keys, and billing from your terminal, and serves Orca to coding agents over MCP. It is a single binary; it does not need Node.
Install
On macOS and Linux:~/.local/bin/orca. To pin a version, set ORCA_VERSION=cli-v1.0.0; to install somewhere else, set ORCA_INSTALL_DIR.
On Windows, download orca-windows-x64.tar.gz from the releases page.
Check it worked:
Update
orca update needs no login. An older CLI that talks to Orca 2.0 is told “This CLI is too old for Orca. Run orca update.” On Windows, a running .exe cannot replace itself, so download the new release instead.
Sign in
- It prints the code and a link to the dashboard: “First, copy your one-time code”, then “Then open:” and the link. In a terminal it opens the link for you.
- In the dashboard, check that the code matches and choose Approve. See approve a CLI login.
- The CLI receives a new API key with your role and stores it. It prints “Logged in to Orca as” your role and organization.
--no-browser to only print the code and link. The login is named after the machine, such as “CLI on laptop”; change it with --label.
orca auth logout forgets the key on this machine only; the key keeps working.
Where the CLI keeps its key
Keys are stored per context in~/.config/orca/config.json, readable only by you. A context is a named API URL and key, like a kubectl context: orca context list, orca context use <name>, or --context <name> on one command. The default API URL is https://api.orcapods.ai.
Use it in CI
CI needs no config file. Set the key in the environment:orca keys create ci. To store a key without the code flow, use orca login --with-token orca_sk_....
A flag wins over an environment variable, which wins over the config file.
Check your setup
orca doctor checks the config file, the server, your key and role, and your credit, and prints a fix for each problem it finds. It only reads; it never creates anything.
Next: commands, or use Orca from Claude Code, Cursor, and Codex.