@argosvix/cli

@argosvix/cli

One-command onboarding for Argosvix — AI agent observability.

npx @argosvix/cli init

init does the whole setup for you:

• Opens your browser to approve once (creates an account-scoped API key — the only manual step).
• Installs the SDK (@argosvix/sdk for Node, argosvix for Python).
• Writes ARGOSVIX_API_KEY to .env (and adds .env to .gitignore).
• Wires the Argosvix MCP server into Cursor / Claude Desktop (so you can query and operate your observability data from chat).
• Prints the one-line wrap() snippet to add to your code (or let your AI apply it).
• Sends a test event so you immediately see data in the dashboard.

The browser-issued key is least-privilege (read + write:records = read + ingest only). It cannot change alerts or settings; create a full key from the dashboard if you need one.

Commands

npx @argosvix/cli init           # full setup (browser approve once)
npx @argosvix/cli init --force-login   # re-authenticate even if a key exists
npx @argosvix/cli login          # just (re)authenticate and write .env
npx @argosvix/cli doctor         # diagnose: key / API reachability / MCP / runtime

How auth works (PKCE, no secret paste)

init starts a temporary loopback server on 127.0.0.1, opens https://dashboard.argosvix.com/<locale>/cli/authorize with a PKCE code_challenge

• state, and waits for the browser redirect. You approve in the dashboard; the backend returns a one-time code to the loopback; the CLI exchanges it (with the PKCE verifier) for the API key. The key is never pasted by hand and never leaves your machine beyond the .env you control.

Environment overrides (advanced)

• ARGOSVIX_API_BASE (default https://ingest.argosvix.com)
• ARGOSVIX_DASHBOARD_BASE (default https://dashboard.argosvix.com)
• ARGOSVIX_LOCALE (default en)

Requirements

Node.js >= 20.