CLI

Chat with your agents, run them from scripts and CI, and manage your tenant from the terminal.

ba puts your agents in your terminal. Chat with an agent while you tune its instructions, run it from a script or CI job, or ask the built-in assistant to manage your tenant for you. Everything runs on Blazing Agents, so the CLI never runs tools on your machine.

Install the CLI

You need Node.js 24 or later.

npm install --global @blazingagents/cli@0.1.0
ba --version

You see 0.1.0. Run ba --login next to connect the CLI to your account (see setup and authentication), then chat with the agent from the quickstart:

ba --login
ba chat "Quickstart agent"

A chat window opens in your terminal. Type a message and the answer streams in.

Choose a command

CommandWhat it doesUse it for
ba chat <agent>Opens an interactive chat with one of your agentsTrying out and tuning an agent
ba run <agent>Runs one turn with no interaction and prints the answerScripts, pipes, and CI jobs
ba assistOpens a chat with the built-in assistant that manages your tenantCreating agents, prompts, and tasks, or checking usage, in plain language

Run ba --help or ba <command> --help for every flag. Help never needs a network connection or a stored key.

Choose an agent

ba chat and ba run take an agent ID (ag_...) or the agent's full name. An exact name wins. Otherwise the CLI accepts a single match that ignores case, and lists the candidates with their IDs if there are several. Partial names never match.

The agent needs a provider and model before it can answer. The quickstart agent already has both.

Point the CLI at another API

The CLI talks to https://api.blazingagents.com. To use a different address, pass --base-url, set BLAZING_AGENTS_BASE_URL, or put a baseUrl line in a config file. They win in that order.

config.yaml
baseUrl: https://api.blazingagents.com

The file lives at ~/.config/blazing-agents/config.yaml on macOS and Linux (or under $XDG_CONFIG_HOME if set), and at %APPDATA%\blazing-agents\config.yaml on Windows. It holds only baseUrl, never a key. The CLI never writes to it.

Next

On this page