Skip to main content

Overview

Global options are specified before the command (e.g., single-turn, multi-turn) and apply to all CLI operations.

API Configuration

Circuit Breaker Labs API Key

string
required
Circuit Breaker Labs API key for authentication with the CBL evaluation service.Environment Variable: CBL_API_KEY
Keep your API key secure. Never commit it to version control. Use environment variables or secure secret management.

Circuit Breaker Labs API Base URL

string
default:"https://api.circuitbreakerlabs.com"
Base URL for the Circuit Breaker Labs API endpoint. Typically only changed for custom deployments or testing.Environment Variable: CBL_API_BASE_URL
The default value points to Circuit Breaker Labs’ production API. Only change this if you’re using a custom deployment or testing environment.

Logging Options

Log Level

enum
default:"info"
Sets the logging verbosity level.Available Levels:
  • error - Only critical errors
  • warn - Warnings and errors
  • info - General information (default)
  • debug - Detailed debugging information
  • trace - Very detailed trace information
Use debug or trace level when troubleshooting issues or reporting bugs.

Log Mode

boolean
default:"false"
Enable log mode to disable the interactive TUI and output logs directly to stdout.
Use Cases:
  • CI/CD pipelines
  • Automated scripts
  • Log file generation
  • When running in non-interactive environments
When --log-mode is enabled, the TUI (Terminal User Interface) is disabled and all output goes to stdout, making it suitable for automation.

Output Configuration

Output File

string
Specify a custom path for evaluation results. If not provided, results are saved with an auto-generated timestamp.
Default Format: evaluation_results_YYYY-MM-DD_HH-MM-SS.json
Use descriptive filenames that include dates, model names, or test identifiers for better organization:

Custom Headers

Add Header

string
Add custom HTTP headers to provider requests. Can be specified multiple times for multiple headers.Format: Key:Value
Use Cases:
  • Custom authentication for providers
  • Request tracking headers
  • API version specification
  • Custom routing headers
Custom headers are sent to the provider API (OpenAI, Ollama, or custom), not to Circuit Breaker Labs API.

Complete Examples

Basic Setup with Environment Variables

Production Evaluation with Custom Output

CI/CD Pipeline Configuration

Debug Mode with Verbose Logging

Custom Endpoint with Headers

Multi-Turn with Complete Configuration

Environment Variables Summary

All global options can be set via environment variables:

Setting Environment Variables

Best Practices

Security

Never commit API keys to version control. Use environment variables or secret management systems.

Logging Strategy

Development: Use --log-level debug with --log-mode for detailed troubleshooting.Production: Use --log-level info without --log-mode for the interactive TUI.CI/CD: Use --log-mode with appropriate log level and redirect to files.

Output Organization

Single-Turn

Single-turn command reference

Multi-Turn

Multi-turn command reference

Commands Overview

Overview of all commands