Skip to content

bullpen config show

Last updated: July 13, 2026

Display the current configuration

Usage

bullpen config show [OPTIONS]

Live Help

Display the current configuration

Usage: bullpen config show [OPTIONS]

Options:
      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --env <ENV>
          Target environment to connect to (overrides config.toml)

          [env: BULLPEN_ENV=]
          [possible values: staging, production]

      --config <CONFIG>
          Path to a custom config.toml file (overrides $BULLPEN_CONFIG and the default location).

          Explicit --config and BULLPEN_CONFIG paths fail closed: if the file is missing, the CLI exits validation instead of silently loading defaults. Credentials still resolve via BULLPEN_HOME, so set BULLPEN_HOME too when isolating a session.

      --read-only
          Enable read-only mode: blocks all mutating commands

      --non-interactive
          Suppress interactive prompts; does NOT imply --yes for money-moving commands

          [env: BULLPEN_NON_INTERACTIVE=]

  -h, --help
          Print help (see a summary with '-h')

EXAMPLES:
  # Show the active config
  bullpen config show

  # Export config as JSON
  bullpen config show --output json

Example Commands

bullpen config show
bullpen config show --output json

JSON Output

Contract: JSON Output Contract.

Successful output is a single JSON document. The shape below is representative for this command family; commands may add fields without breaking the shared contract.

Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.

Top-level Keys

key type nullable notes
env string no Active environment after config and CLI overrides are applied
usergate_url string no Bullpen account-service base URL used by authenticated commands
trade_server_url string no Bullpen trade-service base URL
polygon_rpc_url string no Polygon RPC URL after defaults and env overrides are applied; v0.1.102+ redacts token-bearing userinfo, path, query, and fragment details before display
output_format string no Default output format from the active config
credential_store string no Credential store backend selected by config
check_for_updates boolean no Whether update checks are enabled
experimental object yes Raw experimental feature toggles present in config.toml

Example

bullpen config show --output json
{
  "env": "production",
  "usergate_url": "https://usergate.bullpen.fi",
  "trade_server_url": "https://trade-service.bullpen.fi",
  "polygon_rpc_url": "https://polygon-bor-rpc.publicnode.com",
  "output_format": "table",
  "credential_store": "auto",
  "check_for_updates": true,
  "experimental": null
}

Stability

Patch releases may add nullable or optional fields. Minor releases may add required fields or increment schema_version. Major releases may remove or rename fields.