bullpen config telemetry

Last updated: July 13, 2026

Manage privacy-safe telemetry (Sentry + usage analytics opt-out)

Usage

bullpen config telemetry [OPTIONS] <ACTION>

Live Help

Manage privacy-safe telemetry (Sentry + usage analytics opt-out)

Usage: bullpen config telemetry [OPTIONS] <ACTION>

Arguments:
  <ACTION>
          Possible values:
          - on:     Opt in to all telemetry (Sentry errors + usage analytics)
          - off:    Opt out of all telemetry (Sentry errors + usage analytics)
          - status: Show the current telemetry status

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 current telemetry status
  bullpen config telemetry status

  # Opt out of all telemetry
  bullpen config telemetry off

  # Opt back in
  bullpen config telemetry on

See docs/public/telemetry.md for exactly what is and is not collected.

Example Commands

bullpen config telemetry status
bullpen config telemetry off
bullpen config telemetry on
bullpen config telemetry status --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.