bullpen hyperliquid copy pause¶
Last updated: July 13, 2026
Pause a Hyperliquid copy-trading subscription
Usage¶
Live Help¶
Pause a Hyperliquid copy-trading subscription
Usage: bullpen hyperliquid copy pause [OPTIONS] <TARGET>
Arguments:
<TARGET>
Subscription id or copied Hyperliquid leader address
Options:
--no-multi-wallet-warning
Suppress the table-mode warning shown when multiple EVM wallet accounts exist
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--preview
Print the planned pause without changing state
--env <ENV>
Target environment to connect to (overrides config.toml)
[env: BULLPEN_ENV=]
[possible values: staging, production]
-y, --yes
Skip confirmation prompt
--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:
# Preview pausing a subscription without changing state
bullpen hyperliquid copy pause copy-sub-123 --preview
# Export the pause preview as JSON
bullpen hyperliquid copy pause copy-sub-123 --preview --output json
SAFETY:
Hyperliquid copy trading is experimental. Local CLI gates cover
Bullpen service-backed request construction and preview/live gating, but full
production service availability depends on Bullpen account-service enablement.
Example Commands¶
bullpen hyperliquid copy pause copy-sub-123 --preview
bullpen hyperliquid copy pause copy-sub-123 --preview --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.