The open-source command-line interface requires Node.js 24 or newer. Linux
systems also need the libsecret-1-0 runtime package.
- Chat with an Agent in an interactive terminal interface.
- Run one-off prompts from a shell script or CI job.
- Use Agent-assisted workflows from the command line.
- Store sign-in credentials securely in the operating system keychain.
- Target another Blazing Agents deployment with a flag or configuration file.
npm install --global @blazingagents/cli
ba --helpRun without installing globally:
npx @blazingagents/cli --helpba --login
ba assist
ba chat 'Release Agent'
ba run 'Release Agent' --prompt 'Summarize the latest release'Use ba --help or a command-specific --help for every option.
For CI and other headless environments, provide an API key through the process environment:
export BLAZING_AGENTS_API_KEY='ba_...'
ba run 'Release Agent' --prompt 'Give the status' --jsonThe default API is https://api.blazingagents.com. Override it with
--base-url, BLAZING_AGENTS_BASE_URL, or a baseUrl entry in
${XDG_CONFIG_HOME:-~/.config}/blazing-agents/config.yaml.
See the CLI documentation for setup, authentication, command guides, and CI usage.
In ba assist, ask to create an Agent with a Thinking level, read its current
level, set it to a value such as high, or clear it to Provider default.
The hosted Agent Tool accepts thinkingLevel and preserves update approval.
Known capabilities constrain choices; unknown capabilities accept custom
strings that may still be rejected during execution. ba chat and ba run
use the resolved Agent Version's selection without a per-Turn override.
Configure the Admin Agent's own Thinking level in the dashboard or SDK.