bullpen recover funds

Last updated: August 26, 2026

Preview or recover eligible Polymarket funds without changing wallet selection

Usage

bullpen recover funds [OPTIONS]

Live Help

Preview or recover eligible Polymarket funds without changing wallet selection

Usage: bullpen recover funds [OPTIONS]

Options:
      --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]

      --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.

      --include <LIST>
          Comma-separated asset classes to recover: `positions,orders,balances`

          [default: positions,orders,balances]

      --dry-run
          Print the recovery plan without executing. Default behavior unless `--yes`

      --yes
          Required to execute the reviewed plan. Submit JSON reports dry_run=false

      --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 the recovery plan without submitting anything
  bullpen recover funds --dry-run --output json

  # Execute the reviewed recovery plan
  bullpen recover funds --yes

This checks eligible assets on selected and non-selected owned Safe, Proxy,
current Deposit Wallet, deployed legacy Deposit Wallet, and owned address
sources that you directly control. Recovery never changes your selected trading
wallet. Submit only after the dry-run JSON reports root status `ready`, every
executable leg has outcome `supported` and `effective_evidence.submit_authorized`
true, and the source, destination, route, and assets match your intent.
Use `safe_to_retry` only after a live submit reports post-submit retry evidence.

Example Commands

Live: Run the matching preview first. Submit only when it matches the intended target, size, price guards, and account scope.

bullpen recover funds --dry-run --output json
bullpen recover funds --yes

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.