Configuration
Environment variables, configuration files and CI usage for the BreachLine CLI.
On this page
Environment variables
| Variable | Purpose |
|---|---|
BREACHLINE_API_KEY |
A bl_live_ key for non-interactive sign-in. Used when no stored sign-in exists. |
BREACHLINE_API_BASE |
Advanced. Override the LLM gateway base URL (default https://api.breachline.io/api/v1/llm/v1). Your key is sent to this host. Leave unset in normal use. |
BREACHLINE_VERSION |
Installer only: pin the release to install. |
BREACHLINE_INSTALL_DIR |
Installer only: where to install the binary. |
Configuration files
| File | Scope | Contents |
|---|---|---|
~/.config/breachline/ |
User | Your settings and user-scope MCP servers. |
breachline.json or breachline.jsonc in a project (or its .breachline/ folder) |
Project | Project settings. |
.mcp.json in a project |
Project | Project-scope MCP servers, shared with the repository. |
breachline mcp edit --scope user or --scope project opens the right file in $VISUAL or $EDITOR.
Using the CLI in CI
- name: Retest staging
env:
BREACHLINE_API_KEY: ${{ secrets.BREACHLINE_API_KEY }}
run: |
curl -fsSL https://dl.breachline.io/install.sh | sh
export PATH="$HOME/.breachline/bin:$PATH"
breachline run --format json "Retest the findings fixed in this release on staging.example.com. Scope: staging.example.com only." > breachline-events.jsonl
- Store the key as a masked CI secret, scoped to
llm:accessandllm:chat. --format jsonprints one JSON event per line, which is easy to archive or parse.- Pin
BREACHLINE_VERSIONin CI so runs are reproducible.
Removing local data
breachline auth logout signs out and clears all BreachLine data stored on the machine. breachline uninstall removes the CLI; add --keep-config or --keep-data to keep configuration or sessions, and --dry-run to preview.