bullpen notifications preferences update¶
Last updated: May 29, 2026
Update notification preferences
Usage¶
Live Help¶
Update notification preferences
Usage: bullpen notifications preferences update [OPTIONS]
Options:
--global <on|off>
Toggle all notification delivery
[possible values: on, off]
--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]
--telegram <on|off>
Toggle Telegram notifications
[possible values: on, off]
--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.
--inapp <on|off>
Toggle in-app notifications
[possible values: on, off]
--push <on|off>
Toggle push notifications
[possible values: on, off]
--quiet-hours-start <QUIET_HOURS_START>
Quiet-hours start hour, 0-23
--quiet-hours-end <QUIET_HOURS_END>
Quiet-hours end hour, 0-23
--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=]
--quiet-timezone <QUIET_TIMEZONE>
Quiet-hours timezone, e.g. America/New_York
-h, --help
Print help (see a summary with '-h')
EXAMPLES:
bullpen notifications preferences update --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen notifications preferences update [OPTIONS]
bullpen notifications preferences update --help
bullpen notifications preferences update --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.