This feature is in Beta.
GitHub
orq-cli
Installation
~/.orq/bin/orq. Pre-built release binaries for each platform are available on the Releases page.
Quick start
Authentication
The CLI supports two auth methods. Both respect--profile <name> to keep multiple identities (personal account, CI, self-hosted customer) side by side.
- OAuth device login
- API key
~/.orq/sessions/default.json, and picks an active workspace. Re-run orq auth login to refresh the session. Sign out with orq auth logout.Profiles
Every command accepts--profile <name> (or the ORQ_PROFILE env var). Each profile has its own session file at ~/.orq/sessions/<name>.json and its own API key credentials in ~/.orq/credentials.json. The default profile is default.
--api-base-url sets the host to authenticate against for a self-hosted profile at login time; it is stored in the session. After login, every command on that profile automatically routes to the stored host. Override the host for a single call with --server <url> or ORQ_SERVER=<url> without changing the stored session.
Workspaces
Diagnostics
doctor reports the CLI binary and runtime, active profile and session file path, resolved base URLs and their source (flag, session, env, default, derived), auth status, and reachability probes against each endpoint.
Output formats
TOON (Token-Oriented Object Notation) is the default renderer: a compact, human-readable table format. Switch it per call or persist a new default.orq default-format <json|yaml|toon>.
Command reference
Built-in commands
Resource commands
Use--help on any group for the full surface (inputs, body fields, examples):