Skip to main content
Everything the dashboard shows you, from the terminal. The CLI signs in as your real Belvedir account, so it sees exactly the organizations, projects, and keys the dashboard would.
belvedir login opens the Belvedir dashboard, where you’re usually already signed in — click Approve and the terminal is in. Email/password accounts can skip the browser entirely: belvedir login --email you@example.com. The session lives in ~/.config/belvedir/credentials.json, refreshes automatically, and belvedir logout forgets it.

Operating systems

The CLI runs anywhere Node 18+ does: macOS, Linux, and Windows.
  • Windows needs @belvedir/cli 0.3.3 or newer for browser sign-in; older versions crash while opening the browser. Update with npm install -g @belvedir/cli. Credentials are stored at .config\belvedir\credentials.json under your user profile folder (set XDG_CONFIG_HOME to relocate them on any OS).
  • Headless or remote machines (SSH, containers): if no browser opens, copy the approve URL the terminal prints into a browser on any device; the terminal polls for up to 10 minutes, then the approval link expires. Re-run belvedir login if it timed out.

Reading your data

Projects are referenced by UUID or by name when it’s unambiguous. Every read takes --json for raw output ready to pipe into jq, and list reads take --n <count> (default 20, max 200).

Acting

Training and benchmark runs are currently free (only inference bills, exactly like the dashboard); write commands re-verify the same authorization as their dashboard equivalents (project visibility, key ownership, org owner/admin roles). Destructive commands require a literal --yes. Browser-side flows (buying credits, connecting GitHub) print a URL and open it — the flow finishes on the web. One deliberate gap: belvedir keys create doesn’t exist — API keys are minted in the dashboard (Platform → API Keys), where the raw key is shown once.

Using with coding agents

If an AI coding agent will run belvedir, sign in with belvedir login --readonly: the session is marked server-side and every write command (approving proposals, launching paid runs, changing members or routing) is rejected at the platform, even if something bypasses the CLI and calls the API directly. Prefer a member account with project exclusions over the org owner’s account for agent machines, and never approve a cli-auth link you didn’t initiate — the approve page shows a verification code that must match the one your terminal printed.

Notes

  • Requires Node 18 or newer. The package has no dependencies.
  • Sending traces is not the CLI’s job — that’s the belvedir SDK.
  • Self-hosted or staging platform: belvedir login --platform https://your-host.