CLI

ba is the npm-installed Blazing Agents CLI for interactive Agent chat, platform administration, and one-Turn automation. It is a client of the hosted platform: Agents, Sessions, Tools, execution, and usage remain on Blazing Agents.

Install the CLI

The CLI requires Node.js 24 or newer. It supports macOS x64/arm64 with Keychain, Windows x64/arm64 with Credential Manager, and glibc Linux x64/arm64 with libsecret and a working desktop D-Bus Secret Service. Musl Linux, Alpine, and headless native credential stores are unsupported; use environment authentication for headless automation.

npm install --global @blazing-agents/cli
ba --version
ba --help

You should see the installed version, followed by help that lists assist, chat, and run.

Choose a command

CLI setup and authentication

Authenticate a workstation or a headless environment without putting credentials in configuration.

ba chat

Hold an interactive terminal conversation with an ordinary Agent.

ba run

Execute exactly one Turn for a script, pipe, or CI job.

ba assist and Admin Agent

Administer Tenant resources conversationally with durable Tool approval.

Scripting and CI

Build a secret-safe, machine-readable automation job.

Command	Input and interaction	Session behavior	Intended use
`ba chat <agent>`	Interactive TTY	Creates on the first successful Turn or resumes `--session`	Ordinary Agent conversations
`ba run <agent>`	Literal input, non-TTY stdin, or a stored Prompt; no TUI	Stateless by default; resumes only an explicit `--session`	Scripts and CI
`ba assist`	Interactive TTY	Creates or resumes an Admin Agent Session	Tenant administration

Configure the API origin

The default API origin is https://api.blazing-agents.dev. An optional strict YAML file may contain only a baseUrl property, for example baseUrl: https://api.blazing-agents.dev.

On macOS and Linux, the file is ${XDG_CONFIG_HOME:-~/.config}/blazing-agents/config.yaml. On Windows, it is %APPDATA%\blazing-agents\config.yaml (falling back to the user's AppData Roaming directory).

Origin precedence is --base-url, then BLAZING_AGENTS_BASE_URL, then YAML, then the default. The CLI reads but never creates or rewrites this file, and configuration never contains credentials.

Get help

Run ba --help, ba chat --help, ba run --help, or ba assist --help. Shipped help is authoritative for command flags; help and version output do not load configuration, credentials, the TUI, or the network.

Operational boundaries

Agent selection accepts an exact Agent ID or full name. An ID-shaped value is ID-only; otherwise an exact-case full name wins, followed by one case-insensitive full-name match. Ambiguous names fail and list their exact candidates.

The CLI sends requests to hosted Agents and never executes their Tools locally. Cancellation aborts the active client request, but cannot undo a Tool side effect that already completed. Use the TypeScript SDK or REST API when application code needs resource methods, custom UI, or control beyond one CLI process.

CLI