bullpen hyperliquid copy stop

Last updated: July 13, 2026

Stop a Hyperliquid copy-trading subscription

Usage

bullpen hyperliquid copy stop [OPTIONS] <TARGET>

Live Help

Stop a Hyperliquid copy-trading subscription

Usage: bullpen hyperliquid copy stop [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 stop 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 stopping a subscription without changing state
  bullpen hyperliquid copy stop copy-sub-123 --preview

  # Export the stop preview as JSON
  bullpen hyperliquid copy stop 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 stop copy-sub-123 --preview
bullpen hyperliquid copy stop copy-sub-123 --preview --output json

JSON Output

Contract: JSON Output Contract.

Live --yes --output json output uses this stop result shape:

{
  "kind": "hyperliquid_copy_stop_result",
  "schema_version": 1,
  "status": "stopped",
  "id": "copy-sub-123",
  "subscription_id": "copy-sub-123",
  "target": "copy-sub-123",
  "stopped_at": null,
  "updated_at": "2026-06-30T12:34:56.789Z",
  "observed_at": null,
  "readback_status": "matched_stopped"
}

updated_at comes from post-stop subscription readback. If readback is unavailable, does not find the subscription, or returns no backend timestamp, updated_at is null and observed_at is an RFC3339 UTC timestamp from the CLI process. stopped_at remains null unless the backend returns a dedicated stop timestamp in a future version.

readback_status is one of:

• matched_stopped
• matched_not_stopped
• not_found
• unavailable

Error output follows the shared JSON output contract linked above.

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.