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:
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:
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:
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:
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:
- Run
bullpen tracker copy list --output json. - Run
bullpen tracker copy risk --output json. - Preview
tracker copy startortracker copy editwith--dry-run --output json. - Show the trader address, sizing, execution mode, and risk limits to the user.
- Submit only after explicit approval with
--yes. - Use subscription ids from JSON output for edit, pause, resume, stop, delete, status, and stats.
- If confirmation mode is enabled, inspect
pending --output jsonbefore runningconfirmorreject.
Boundaries¶
tracker copyis Prediction (Polymarket)-only.- Perps copy trading uses
hl copy. --non-interactivesuppresses prompts. It does not imply--yes.- Turnkey policy denials such as
ACTIVITY_TYPE_SIGN_RAW_PAYLOAD_V2require 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.