> ## Documentation Index > Fetch the complete documentation index at: https://docs.orcapods.ai/llms.txt > Use this file to discover all available pages before exploring further. # CLI commands > Every command in CLI 1.0, grouped by what it manages, with output and exit codes. Run `orca --help` for every flag. Where a command takes `[agent]` or another positional in brackets, leaving it out in a terminal opens a picker; in a script it is required. An `` is an agent ID or the name of exactly one agent. ## Sign-in and setup ```text theme={"dark"} orca login | orca auth login [--api-url u] [--label l] [--no-browser] [--with-token orca_sk_...] orca whoami | orca auth whoami orca auth status orca auth logout [--revoke] [--yes] orca context list | use [name] | show orca doctor [--strict] orca update [--check] [--tag t] [--force] ``` See [install and sign in](/cli/install). ## Chat ```text theme={"dark"} orca chat [agent] [prompt...] [--session id] [--sandbox] [--template id] [--vault id]... ``` * **With no prompt** in a terminal, `orca chat` opens a conversation. Ctrl-C cancels a running turn on the server, then exits and prints the command that resumes the session. * **With a prompt or piped input** it runs one turn and streams the answer to stdout. The session ID goes to stderr, so a script can continue with `--session`. * Without `--session` it creates a session first, with no sandbox. `--sandbox` gives it a managed sandbox, `--template` builds the sandbox from an environment template, and `--vault` lets its tools use a vault's credentials. ```bash theme={"dark"} orca chat support # a conversation orca chat support "summarize the open tickets" # one turn echo "and the oldest?" | orca chat support --session sess_123 ``` When a turn ends because Orca credit or your provider account's quota ran out, `orca chat` in a terminal says which, shows the warning about switching, and asks whether to top up or switch who pays for this session. Outside a terminal it prints the reason and the session ID and exits 1. See [switch who pays](/providers#switch-who-pays-for-one-session). ## Agents and sessions ```text theme={"dark"} orca agents list orca agents get [agent] orca agents create -f agent.yaml # YAML or JSON; - reads stdin orca agents update -f fields.yaml # only the fields in the file change orca agents delete [agent] [--yes] orca sessions list [--agent agent] orca sessions get # includes the session's cost, tokens, and machine time orca sessions create --agent [--sandbox] [--template id] [--vault id]... orca sessions items [--limit n] orca sessions delete [--yes] ``` The file for `agents create` is the body of `POST /v1/agents`. The model says who pays: ```yaml theme={"dark"} model: orca/openrouter/openai/gpt-5.6-luna # or anthropic/claude-sonnet-4-5 on your Anthropic key name: support instructions: | You answer support questions. reasoning: { effort: medium } ``` In a terminal, a file with no `model` opens a picker of every model you can use, grouped by who pays. The server checks every field and the CLI prints its message. See [models and provider keys](/providers). ## Skills, vaults, and files ```text theme={"dark"} orca skills list | get | delete [--yes] orca skills create # a folder with SKILL.md orca vaults list | create | delete [--yes] orca vaults credentials list orca vaults credentials add --name n --server https://... [--token t] orca vaults credentials delete [--yes] orca files list orca files upload [--name filename] orca files download [-o path|-] orca files delete [--yes] ``` Creating and deleting vaults and credentials needs the admin role. `credentials add` reads the token from `--token`, stdin, or a hidden prompt. ## Kits ```text theme={"dark"} orca kits list orca kits make --name n [--description d] [--author who] [--readme file] [--agent a]... [--skill id]... [--template id]... orca kits edit [same flags] # a selection flag replaces the whole selection orca kits publish | withdraw orca kits show # no login needed orca kits copy [--name key=name]... [--skip key]... [--dry-run] [--yes] ``` See [kits](/kits). ## API keys ```text theme={"dark"} orca keys list orca keys create [name] orca keys revoke [--yes] ``` `keys create` prints the key once. In a pipe, stdout carries only the key: `ORCA_API_KEY=$(orca keys create ci [--no-open] orca billing manage [--no-open] # the billing portal ``` `billing buy` and `billing manage` need the admin role. They print the Polar link and open it in a browser. See [wallet and credit](/wallet) and [plans](/plans). ## MCP server ```text theme={"dark"} orca mcp serve ``` See [use Orca from coding agents](/cli/mcp). ## Output * `--json` on any list or get command prints the raw API response. * When stdout is not a terminal, output is plain tab-separated lines, so `orca agents list | cut -f1` works. * List commands take `--limit N` (1 to 100, default 10), `--after `, and `--all`. | Exit code | Meaning | | - | - | | `0` | Success | | `1` | API or network error, or a chat turn failed | | `2` | Usage or validation error | | `3` | Missing or invalid key, or not allowed for your role | | `4` | Not found, or gone | | `130` | Interrupted with Ctrl-C | ## Commands that ended CLI 1.0 removed the commands for features that ended with Orca 1.x: `run` and `runs`, `pools`, `workflows`, `memory`, `storage`, `stats`, `topology`, `bundles`, `apps`, `secrets` (now `vaults`), `credit`, `billing cap`, `agents publish` and `agents keys`, and the MCP server catalog (`mcp list`, `mcp add`, and the rest). `kit add` is now `kits copy`. Running one of them gives `unknown command`. See [bring your agents to the new Orca](/migration). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.