Install the Veirox CLI

Pick your package manager

Same binary, same signature, same release tag.

Homebrew (macOS & Linux)

Tap our formula and install. Updates flow through brew upgrade like every other tool you have.

1

Install

brew install veirox-cloud/veirox/veirox

2

Verify

veirox version
veirox doctor

Expect veirox version v0.5.x and a green checklist for keychain, network, and config.

3

Authenticate

veirox login

Opens a browser tab to /console/cli-grant?user_code=…. Approve the device. The CLI stores the resulting ops_k_… key in your OS keyring (macOS Keychain · Linux libsecret).

Scoop (Windows)

Lightweight, portable installs. Updates via scoop update veirox.

scoop bucket add veirox https://github.com/msrashed2018/scoop-veirox
scoop install veirox

Tested on PowerShell 7+ and Windows Terminal. The CLI uses Windows Credential Manager for keyring.

curl | sh (any Unix)

For containers, CI runners, dotfiles bootstraps — anywhere a package manager is overkill.

curl -fsSL https://veirox.com/cli/install.sh | sh

The installer auto-detects $(uname -m), downloads the right binary into ~/.local/bin (or /usr/local/bin with sudo), verifies SHA-256 + cosign signature, and prints the version on success.

CI tip: pin the version explicitly so a new release can't break a deterministic pipeline:

curl -fsSL https://veirox.com/cli/install.sh | sh -s -- --version v0.5.0

Docker (distroless)

Pre-baked image for CI containers. Distroless base — no shell, no apt, no surprises.

docker run --rm -it \
  -v "$HOME/.config/veirox:/home/nonroot/.config/veirox" \
  ghcr.io/veirox-cloud/veirox-cli:latest \
  whoami

Mount $HOME/.config/veirox so your profile + keyring entries survive between runs. Tags: latest, v0.5, v0.5.0, nightly.

First run, in 90 seconds

After install, three commands take you from a fresh shell to a fully wired project with MCP tooling in your editor.

1

Login

veirox login

Opens browser, mints an org-scoped ops_k_… key into your OS keyring.

2

Init

veirox init

Detects git remotes, kubectl context, AWS profile. Creates a project. Seeds runbooks.

3

MCP setup

veirox mcp setup

Wires Cursor, Claude Code, Codex via deeplinks & native CLIs. No JSON to edit.

Then — every day:

# Tail the latest agent session as it runs
veirox tail

# Trigger a task from CI with a deterministic key
veirox task run prod-rollback-check --idempotency-key "$BUILD_ID" --wait

# Stream events as ndjson into your log pipeline
veirox logs --follow --plain | jq -r 'select(.type=="tool") | .text'

# Approve a pending action from the terminal
veirox approval approve <uuid> --comment "lgtm"

36 commands, organised the way you work

Every command emits pretty output by default and JSON / ndjson on -o json, so the same surface drives both humans and CI.

Identity

veirox login · logout · whoami
veirox org list · use · members
veirox api-key create · rotate · revoke
veirox use <profile>

Project resources

veirox project list · create · delete
veirox repo add · test · remove
veirox secret put · get · list · rm
veirox connector add · enroll · revoke

Automation

veirox task list · new · run --wait
veirox session list · info · cancel
veirox agent run <prompt>
veirox reminder · todo · approval

Live

veirox logs <id> --follow
veirox tail
veirox watch tasks|sessions|connectors

Integrations

veirox mcp setup · print · doctor
veirox webhook list · test · rotate
veirox notify · file · artifact

Admin

veirox audit list · stats · export
veirox governance retention · dsr · pii
veirox billing · dashboard · report

Read the full guide

Stuck?

veirox doctor diagnoses the most common issues. If something else trips you up, open an issue or ask the agent.

Open a GitHub issue Ask in the chat

Install the Veirox CLI.