`bullpen support bundle`¶

Last updated: August 26, 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
          Compatibility flag accepted as a passive no-op; support bundles do not refresh auth, wallet, or balance evidence

      --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
          Compatibility flag accepted as a passive no-op; also accepts --include-clob-credit and reports order-credit as not_checked

      --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 passive JSON diagnostic bundle for Bullpen support
  bullpen support bundle --output json

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

Example Commands¶

bullpen support bundle --output json

Support Artifact Handoff¶

bullpen support bundle creates a redacted JSON file on local disk and prints its path. This file is on this machine and has not been uploaded. Attach the JSON file to your support ticket; pasting the local path alone does not send the file to Bullpen.

JSON output includes delivery.state: "local_file_not_uploaded", delivery.uploaded: false, delivery.artifact_path, the compatibility top-level artifact_path, and optional originating_context with only the recent command family and typed error code.

Support bundle handoff is passive and redacted. It does not refresh auth, request a signing probe, or run the per-wallet order credit probe. For active order-credit evidence, use bullpen polymarket wallet-audit --refresh --include-order-credit --output json; for supported on-chain consolidation or recovery, use the command printed by bullpen fix --refresh or bullpen recover funds --dry-run --output json.

On bullpen support bundle, --refresh, --include-order-credit, and --include-clob-credit are passive compatibility no-ops. They are accepted for older scripts but do not change collection behavior and do not prove refreshed auth, signing capability, or order credit.

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.

bullpen support bundle¶