Skip to content

Prediction Copy Trading

Use Prediction copy trading when you want Bullpen to follow Polymarket prediction-market traders through the tracker copy command family. This is separate from Perps copy trading, which lives under hl copy.

Start read-only, preview the subscription, choose whether executions need manual confirmation, then set risk limits before unattended use.

Before You Start

Sign in and confirm the CLI can read your account:

bullpen login
bullpen status --output json
bullpen doctor auth --output json

Inspect current copy-trading state:

bullpen tracker copy list --output json
bullpen tracker copy risk --output json
bullpen tracker copy pending --output json

These commands do not create subscriptions, approve copied trades, or change risk settings.

Preview A Subscription

Preview the trader address before creating a subscription:

bullpen tracker copy start 0x1111111111111111111111111111111111111111 \
  --amount 10 \
  --execution-mode confirm \
  --dry-run \
  --output json

Review the source address, sizing, execution mode, risk limits, and any warning fields. --dry-run validates the plan without creating a subscription.

Use --execution-mode confirm when copied trades should wait for explicit approval. Use automatic execution only after risk limits are configured and the subscription has been tested with small amounts.

Create Or Update

Create the subscription after reviewing the preview:

bullpen tracker copy start 0x1111111111111111111111111111111111111111 \
  --amount 10 \
  --execution-mode confirm \
  --yes \
  --output json

List subscriptions and save the returned subscription id:

bullpen tracker copy list --output json
bullpen tracker copy status <SUBSCRIPTION_ID> --output json

Edit, pause, resume, stop, or delete by id:

bullpen tracker copy edit <SUBSCRIPTION_ID> --amount 8 --yes --output json
bullpen tracker copy pause <SUBSCRIPTION_ID> --yes --output json
bullpen tracker copy resume <SUBSCRIPTION_ID> --yes --output json
bullpen tracker copy stop <SUBSCRIPTION_ID> --yes --output json

Use delete only when you intend to remove the subscription record rather than stop copying.

Risk Limits

Set account-level risk limits before enabling unattended execution:

bullpen tracker copy risk set \
  --max-per-trade 25 \
  --daily-limit 100 \
  --max-open-positions 5 \
  --yes \
  --output json

Review or reset risk state:

bullpen tracker copy risk --output json
bullpen tracker copy risk reset --yes --output json

tracker copy risk set uses --max-per-trade. The similarly named --max-trade-size flag belongs to subscription start/edit, not the risk config command.

Manual Confirmations

If a subscription uses confirmation mode, review pending executions before approving or rejecting them:

bullpen tracker copy pending --output json
bullpen tracker copy confirm <EXECUTION_ID> --yes --output json
bullpen tracker copy reject <EXECUTION_ID> --yes --output json

For live monitoring in a terminal:

bullpen tracker copy watch

Agents should prefer pending --output json plus explicit confirm or reject calls over interactive watch mode.

Before confirming, inspect the market identity in the pending execution. When market metadata is sparse, the CLI still exposes lower-level source_condition_id and source_token_id fields in JSON and shows them in the confirmation preview.

Agent-Safe Workflow

Agents should use this sequence:

  1. Run bullpen tracker copy list --output json.
  2. Run bullpen tracker copy risk --output json.
  3. Preview tracker copy start or tracker copy edit with --dry-run --output json.
  4. Show the trader address, sizing, execution mode, and risk limits to the user.
  5. Submit only after explicit approval with --yes.
  6. Use subscription ids from JSON output for edit, pause, resume, stop, delete, status, and stats.
  7. If confirmation mode is enabled, inspect pending --output json before running confirm or reject.

Boundaries

  • tracker copy is Prediction (Polymarket)-only.
  • Perps copy trading uses hl copy.
  • --non-interactive suppresses prompts. It does not imply --yes.
  • Turnkey policy denials such as ACTIVITY_TYPE_SIGN_RAW_PAYLOAD_V2 require account-policy repair by support; repeated login does not grant missing policy permissions.

Generated References

Use generated references for exact flags: tracker copy, start, edit, list, pending, confirm, reject, risk, risk set, and stats.