bullpen tracker copy risk set¶
Last updated: July 13, 2026
Set risk configuration limits
Usage¶
Live Help¶
Set risk configuration limits
Usage: bullpen tracker copy risk set [OPTIONS]
Options:
--max-per-trade <MAX_PER_TRADE>
Maximum USD per individual trade
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--daily-limit <DAILY_LIMIT>
Daily spending limit in USD
--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.
--max-open-positions <MAX_OPEN_POSITIONS>
Maximum number of open positions at once
--restrict-categories <RESTRICT_CATEGORIES>
Comma-separated list of categories to restrict
--consecutive-loss-pause <CONSECUTIVE_LOSS_PAUSE>
Pause after N consecutive losses (0 to disable)
--yes
Skip confirmation prompt
--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:
# Review current copy-trade risk configuration
bullpen tracker copy risk
# Update risk limits; this prompts before changing copy-trading risk settings
bullpen tracker copy risk set --max-per-trade 25 --daily-limit 100 --max-open-positions 5
Example Commands¶
bullpen tracker copy risk
bullpen tracker copy risk set --max-per-trade 25 --daily-limit 100 --max-open-positions 5
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.