Bandwise docs

CLI reference

The bandwise command line, on npm as @bandwise/cli. Local mode works today; the rest arrives in Phase 3.

Coming in Phase 3

The commands that manage sets, publish versions, change rollout stages and run evals over the HTTP API arrive in Phase 3. This page will list every command then.

Install

The CLI is published on npm as @bandwise/cli and needs Node.js 22.13 or later. Run it with npx, or install it once:

npx @bandwise/cli run --local spec.json state.json
npm install -g @bandwise/cli    # then: bandwise run --local spec.json state.json

What works today

One command works now:

bandwise run --local <spec.json> <state.json> [--json]
  [--rollout shadow|controlled|full|paused]
  [--channel production|staging]
  [--provider typesafe|openrouter|vercel]

It runs a spec on a state with fixture answers. It makes no network call and needs no key. See the quickstart.

Conventions the full CLI will follow

  • Every command supports --json for scripts and agents.
  • It never prompts when input is not a terminal. A command that needs confirmation then fails and asks for --yes.
  • Exit codes: 0 ok, 1 error, 2 a diff or drift was found, 3 an approval is pending.
  • It reads BANDWISE_TOKEN and BANDWISE_BASE_URL, or a named profile. It never holds a TypeSafe, OpenRouter or AI Gateway key.

Bandwise is an independent product built on TypeSafe's System One models. It is not TypeSafe's documentation. For the System One models themselves, see docs.typesafe.ai.

Webhooks

Previous Page

Agents and MCP

How agents will run the same loop a person runs in the console. Coming in a later phase.

On this page

InstallWhat works todayConventions the full CLI will follow