CLI — Diagnostics

Two commands give you a fast health picture without opening the dashboard: rivano status for a live overview of your tenant, and rivano doctor for diagnosing connectivity and configuration issues.

rivano status

rivano status shows an at-a-glance dashboard of your tenant’s current state:

rivano status

Output:

Rivano Status
─────────────────────────────────────
Auth:          ✔ Logged in as you@example.com (Pro)
Agents:        3 active (2 production, 1 staging)
Traces:        1,847 total | 97.6% success | avg 381ms
Governance:    Score 82/100 · 4 active policies · 0 open violations
Costs:         $24.18 this month · 0 budget alerts

What status shows

Section	Description
Auth	Current logged-in user and plan
Agents	Count of active agents by environment
Traces	Rolling stats: total, success rate, average latency
Governance	Posture score, active policy count, open violations
Costs	Month-to-date spend, active budget alerts

Use --json to get structured output for monitoring scripts:

rivano status --json

{
  "auth": {
    "email": "you@example.com",
    "plan": "pro"
  },
  "agents": {
    "total": 3,
    "production": 2,
    "staging": 1
  },
  "traces": {
    "total": 1847,
    "successRate": 97.6,
    "avgDurationMs": 381
  },
  "governance": {
    "postureScore": 82,
    "activePolicies": 4,
    "openViolations": 0
  },
  "costs": {
    "monthToDate": 24.18,
    "budgetAlerts": 0
  }
}

rivano doctor

rivano doctor runs five diagnostic checks and reports the result of each:

rivano doctor

Output (all passing):

Rivano Doctor
─────────────────────────────────────
✔ Config      ~/.rivano/config.json exists and is valid JSON
✔ Auth        API key is valid · logged in as you@example.com
✔ Connectivity Can reach api.rivano.ai (145ms)
✔ Providers   1 provider configured (openai) · test passed
✔ YAML        rivano.yaml found in current directory · schema valid

All checks passed.

Output (with failures):

Rivano Doctor
─────────────────────────────────────
✔ Config      ~/.rivano/config.json exists and is valid JSON
✗ Auth        401 Unauthorized — API key is invalid or expired
✔ Connectivity Can reach api.rivano.ai (89ms)
✗ Providers   No providers configured
✔ YAML        rivano.yaml found in current directory · schema valid

2 checks failed. Run `rivano login` to fix Auth.

The 5 diagnostic checks

Check	What it verifies
Config	~/.rivano/config.json exists, is valid JSON, and contains an apiKey field
Auth	The API key authenticates successfully against the control plane
Connectivity	The control plane at api.rivano.ai (or your configured baseUrl) is reachable
Providers	At least one provider is configured and responds to a connectivity test
YAML	rivano.yaml exists in the current directory and passes schema validation

Exit codes

Both commands exit with code 0 on success and 1 on failure, making them composable in shell scripts:

rivano doctor && rivano deploy
# Only deploys if doctor passes

Related

• CLI Overview — Authentication and config file reference
• CLI Deploy — Deploy agents after doctor passes
• Gateway Overview — Gateway-specific health checks