`bullpen tracker copy delete`¶

Last updated: August 26, 2026

Delete a copy trade subscription

Usage¶

bullpen tracker copy delete [OPTIONS] <ADDRESS>

Live Help¶

Delete a copy trade subscription

Usage: bullpen tracker copy delete [OPTIONS] <ADDRESS>

Arguments:
  <ADDRESS>
          Ethereum address of the followed trader

Options:
      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --yes
          Skip confirmation prompt

          [aliases: --confirm]

      --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:
  # Review the subscription before deleting it
  bullpen tracker copy status 0x1111111111111111111111111111111111111111

  # Request deletion; confirmation is required before changing state
  bullpen tracker copy delete 0x1111111111111111111111111111111111111111

Example Commands¶

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

bullpen tracker copy status 0x1111111111111111111111111111111111111111
bullpen tracker copy delete 0x1111111111111111111111111111111111111111

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.