bullpen support bundle

Last updated: July 13, 2026

Build a support-safe diagnostic bundle

Usage

bullpen support bundle [OPTIONS]

Live Help

Build a support-safe diagnostic bundle

Usage: bullpen support bundle [OPTIONS]

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

          [possible values: table, json]

      --output-file <PATH>
          Write the JSON bundle to this path instead of the default support directory

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

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

      --refresh
          Refresh wallet registry and balance evidence while building the bundle

      --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.

      --include-order-credit
          Include deeper order-credit checks for support. This may take longer

      --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:
  # Create a refreshed JSON diagnostic bundle for Bullpen support
  bullpen support bundle --refresh --include-order-credit --output json

  # Write the bundle to a specific file
  bullpen support bundle --refresh --output-file bullpen-support.json --output json

Example Commands

bullpen support bundle --refresh --include-order-credit --output json
bullpen support bundle --refresh --output-file bullpen-support.json --output json

JSON Output

Contract: JSON Output Contract.

This command supports --output json, but this generated reference page intentionally does not include a synthetic success schema or example.

Use the live command in your target environment to inspect command-specific success fields. Error output follows the shared JSON output contract linked above.

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

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.