`bullpen experimental enable`¶

Last updated: August 26, 2026

Enable an experimental feature

Usage¶

bullpen experimental enable [OPTIONS] <FEATURE>

Live Help¶

Enable an experimental feature

Usage: bullpen experimental enable [OPTIONS] <FEATURE>

Arguments:
  <FEATURE>
          Feature name (e.g. device_login)

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:
  # Enable prediction analytics
  bullpen experimental enable prediction_analytics

  # Enable prediction analytics and emit JSON
  bullpen experimental enable prediction_analytics --output json

Example Commands¶

State change: One or more examples below change account or trading state. Run only the command that matches your intended action.

bullpen experimental enable prediction_analytics
bullpen experimental enable prediction_analytics --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
`status`	string	no	`enabled` or `disabled` after the config update succeeds
`feature`	string	no	Feature name supplied on the command line
`message`	string	no	Human-readable result returned by the config layer

Example¶

Example output: This non-runnable command-and-response pair documents the JSON shape. Use the preview/live workflow in Example Commands when you intend to submit.

bullpen experimental enable prediction_analytics --output json

{
  "status": "enabled",
  "feature": "prediction_analytics",
  "message": "Enabled experimental feature: prediction_analytics"
}

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 experimental enable¶