Skip to content

Roadmap

This page explains the public boundary of the current Bullpen CLI release. It does not replace the Changelog or the generated Command Reference.

Current Release

v0.1.114 is the current CLI usability and support-readiness release for Bullpen's three product areas: Onchain (Solana), Perps (Hyperliquid), and Prediction (Polymarket). It keeps the existing trading surfaces and makes the normal path simpler: log in, check status, run fix if the CLI reports a problem, use simple trade and recovery commands first, and send one support artifact when the account needs Bullpen-side help.

Area Current public scope Start here
Perps (Hyperliquid) Read markets/account state, preview and submit supported long/short/close/scale/TWAP flows and TP/SL placement. TP/SL modify/clear are implemented; use small sizes and confirm cleanup after live changes. Perps First Trade
HIP-3 Discover DEXes, read selected DEX markets, and submit supported selected-DEX perp mutations with explicit --dex or <DEX>:<SYMBOL> scope. HIP-3 Perps Trading
Spot (Hyperliquid) Discover pairs, inspect books/orders/fills, submit spot buy/sell, cancel, cancel all, use spot scale, and use spot TWAP create/cancel. Spot (Hyperliquid)
Pear Set up Pear, open/close pair trades, read positions/orders/TWAPs, update risk, adjust leverage, cancel orders, and check cleanup state. Pear Pair Trading
Perps copy trading Preview/create/update/pause/resume/stop subscriptions, configure risk, review pending executions, inspect stats, and check cleanup state. Perps Copy Trading
Prediction copy trading Use tracker copy for prediction-market copy subscriptions, manual confirmations, and risk limits. Prediction Copy Trading
Onchain (Solana) Use experimental token reads, previews, swaps, withdraws, limit orders, DCA, history, and stats with small test amounts first. Onchain Solana First Trade
Cross-product watchlist Bookmark Prediction events, Onchain Solana tokens, Hyperliquid perps/HIP-3 symbols, and Hyperliquid spot tokens under tracker watchlist. Orders and Watchlist

Still Limited

Some surfaces remain intentionally narrow because they need more service support, market support, account-specific confirmation, or real-account testing:

  • Signed all-DEX Hyperliquid write fanout is not exposed. Choose one DEX per mutation.
  • HIP-3 copy filters are not part of the current Hyperliquid copy-trading support.
  • Pear pre-submit rebalance and risk/leverage edits are supported. Post-open rebalance and richer watch/detail behavior remain follow-up work.
  • Some HIP-3 DEXes can expose prices or previews while rejecting live orders for account/market reasons such as insufficient usable margin. JSON mode returns HYPERLIQUID_MARGIN_INSUFFICIENT for that class.
  • Spot modify remains outside this release line.
  • Vault/HLP write management, managed API-wallet management, Unit/Hyperunit external flows, and routing-recovery signing are not public CLI surfaces.
  • Account-specific Prediction wallet registration, balance attribution, and recovery states are support-gated when bullpen fix --refresh cannot prove a safe local action. Run bullpen support to create one redacted artifact.
  • A rejected refresh token is reported as login-required. If a fresh login is also rejected, use bullpen support; deleting credential files or repeatedly logging in will not repair an account-side session problem.
  • Solana is experimental. Use previews, keep first trades small, and check post-trade balances before chaining actions.

Next Planning Focus

The next planning cycle focuses on:

  • hardening long-running auth sessions so power users do not need unnecessary relogins;
  • continuing Solana service-readback polish for DCA future-start schedules, token-whale upstream availability, and post-trade balance lag;
  • adding service support for HIP-3-aware copy filters and richer Pear detail, watch, and rebalance flows;
  • keeping public docs task-first while generated reference remains the source of truth for flags and command syntax;
  • confirming account-specific Prediction wallet, redeem, and stranded-fund outcomes with affected users after the CLI has produced a support artifact.

Release Policy

  • A feature is public release scope only when it has command docs, JSON/table output behavior, preview or dry-run behavior where applicable, and regression tests.
  • Bugs in shipped surfaces can move into the active release when they have a clear reproduction and a bounded fix.
  • New product surfaces stay in the next release unless the release owner explicitly changes scope.
  • Public release notes should mention both shipped functionality and major surfaces that are not available yet or are not ready for broad release.