The CLI

@operio/cli is the official command-line client for Operio. It talks to the same API as the web app, so anything you create from the terminal shows up in the UI immediately.

What it's good for

• CI gates — run a suite and fail the build if anything breaks, in one command.
• Tests in your repo — keep test cases as JSON next to the code they cover.
• Bulk work — creating twenty environments is a for loop, not twenty trips through a UI.
• AI agents — JSON output and stable exit codes let an agent run tests and read results on its own. See Agentic Usage.

Install

Requires Node.js 18 or newer.

npm install -g @operio/cli

pnpm add -g @operio/cli

yarn global add @operio/cli

npx @operio/cli whoami

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

Authenticate

operio auth login

This opens your browser to Operio's consent screen. Click Allow and you're done — you never type a password into the terminal.

✓ Logged in as you@example.com (Acme Inc.)

Your session is stored under ~/.config/operio/ and refreshes itself as you work.

operio auth status     # who you're signed in as
operio auth logout     # 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

operio whoami is the fastest way to answer "why is this hitting the wrong project?". JSON (the default) reports your account alongside the selected team and project by name:

{
  "email": "qa@example.com",
  "organizationName": "Acme",
  "team": { "id": "…", "name": "Default Team" },
  "project": { "id": "…", "name": "Checkout" }
}

--output table prints a greeting instead:

Logged in as Ada Lovelace (ada@example.com) 👋
Team: Default Team
Project: Checkout

If a selection shows "available": false, it points at something this account can no longer reach — pick a new one with teams use / projects use.

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> --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