Set up the CLI

Use @operio/cli to manage tests and builds, run suites in CI, and inspect results. Changes appear in the web app.

Install

Requires Node.js 18 or newer.

npm install -g @operio/cli

A global install also puts op on your PATH — it is an alias for operio.

Authenticate

operio auth login

Approve access in the browser. Your session is stored under ~/.config/operio/ and refreshes automatically.

Use operio auth status to check your account and operio auth logout to clear stored credentials.

Select a project

Most commands act on a project. Pick one once instead of passing --project-id every time:

operio teams list
operio teams use <team-id>

operio projects list
operio projects use <project-id>

operio whoami      # who you are, and what's currently selected

Use operio whoami to confirm the selected account, team, and project. If a selection reports "available": false, select a resource your account can access.

Use IDs returned by the matching list command; names are not resolved to IDs.

Output

Commands print JSON to stdout; progress and errors go to stderr, so redirection gives you a clean file.

operio tests list > tests.json           # JSON (default)
operio --output table tests list         # human-readable
operio --quiet tests run <id> --environment-id <env-id> --wait     # no progress chatter

List commands return compact summaries. Add --full on a detail command when you need the complete record:

operio runs get <run-id> --full

Passwords, tokens, and environment variables are stripped from every output format.

Exit codes

This is what makes --wait usable as a CI gate:

operio suites run <suite-id> --environment-id <env-id> --wait

Next steps

• Browse the command reference
• Set up an AI agent to run tests for you
• Connect a client to the hosted MCP server instead of the CLI