bitspark-agw — Agent Gateway CLI

agw sets up and manages your project's connection to a Claude Gateway: wire a project through the gateway, manage your projects and credentials, and read your usage — from one small binary.

Install

npm i -g bitspark-agw
agw --version

Requires Node 24+.

Quick start

# Point at your gateway (adminUrl = management API, compatUrl = the Anthropic-compatible proxy)
agw target add local --admin-url http://127.0.0.1:3301 --compat-url http://127.0.0.1:3300
agw target use local

agw init       # mint a project credential → write .claude/settings.local.json
agw status     # this project's wiring + today's spend
agw runs       # run history            agw tail   # live run events
agw usage      # today's spend + budget

agw --help     # full command list        agw completion bash   # shell completion (also zsh|fish|pwsh)

For agents/CI, agw init wires a credential into .claude/settings.local.json — no login needed. Logging in with an account (agw login) resolves your role and adjusts the available surface automatically; the gateway server is always the enforcement boundary. agw login defaults to a browser-delegated sign-in (approve in the console — no password typed, 2FA/SSO handled there, works headless); pass --classic for the email+password flow. Sessions are stored per target.

Configuration

agw stores named environments and your session under ~/.agw/. Endpoint resolution precedence: --base-url/--target flags ▸ a per-project .agw.json ▸ ~/.agw/config.json ▸ AGW_* env vars. Run agw target show to see what resolves for the current directory.