Changelog¶
Bullpen is still Alpha. These notes are written for CLI users: what changed, what is safer, and what remains limited. Detailed engineering records stay out of the public changelog.
v0.1.114 - 2026-07-14¶
v0.1.114 makes the normal Bullpen journey simpler and safer: log in once, check local session state, refresh account readiness when needed, trade from the wallet Bullpen currently selects, recover older funds explicitly, and create one redacted support artifact when an account needs help.
Highlights¶
- One repair command for common account issues.
bullpen fixnow uses the shared recovery planner and prints one safe next command instead of exposing wallet-routing internals first. - Trading follows the wallet selected for your account. Prediction order, approval, cancellation, collateral conversion, and position-split paths preserve that wallet through confirmation and submission. Older wallets remain available only through explicit fund-recovery flows.
- Simple Prediction trade and recovery wrappers are documented first.
bullpen trade buy,bullpen trade sell,bullpen recover polymarket,bullpen recover funds, andbullpen recover redeemroute through the same underlying safeguards as the expert Polymarket commands. - Support handoff is one command.
bullpen supportrefreshes auth when safe, collects a redacted artifact, and prints a support-ready summary. - Money-path errors share one recovery shape. Polymarket CLOB, wallet route,
redeem, and recovery failures now expose a canonical
recoveryorrecovery_planobject in JSON while terminal output stays short. - Status is passive and predictable.
bullpen statusreads local session state without refreshing credentials or changing wallet state. Runbullpen fix --refreshwhen you need current account and trading-readiness checks. - Auth state is protected from local-build and concurrency mistakes. Local development builds cannot overwrite normal release credentials, TUI startup stays read-only, sensitive TUI input and history are redacted, and overlapping login, refresh, and logout operations keep the newest valid session. Device login now has bounded progress and stall reporting instead of waiting forever.
- Ambiguous recovery failures stop safely. Redeem and collateral recovery no longer try a different money-moving route after an uncertain submission outcome. The CLI returns the original error and one safe next action.
- Resolved-position and redeem output is clearer. Position rows separate
actionable
redeemablevalue from upstream provider hints, and redeem output separates confirmed transaction receipts from still-unproven balance movement. - Small-price Prediction markets are handled consistently. Preview and submit share the same valid tick-size parser and use bounded cached metadata only when the provider retry path cannot return a fresh value.
- Solana swaps have better after-trade guidance. Post-swap output waits longer for balance readback and reports dust that is too small to clean up economically.
- Pear read-session errors point to the right command. Missing or expired
Pear read sessions now point to
bullpen hl pair login --yes, not live setup, unless setup diagnostics say setup is actually incomplete. - Agent skills now teach the same journey. The maintained skills lead with
login,
status,fix, simple trade, recovery, and support handoff before advanced wallet diagnostics.
Still Limited¶
- A service-rejected refresh token is now reported as a login-required state, but a rejection before the visible session expiry can still require Bullpen support to investigate the account session.
- Device login now stops with a clear stalled state instead of waiting forever, but a browser approval that never reaches a completed service state can still require Bullpen support.
- Some account-specific wallet registration, trading-balance attribution,
signing permission, and dashboard-sync problems still require Bullpen
support. Run
bullpen fix --refresh; if it directs you to support, runbullpen supportonce instead of repeating login, approval, or wallet-change commands. - Solana remains experimental. Preview first, use small sizes, and check balances after live actions.
v0.1.112 - 2026-07-06¶
v0.1.112 is a support-hardening follow-up to v0.1.111. It keeps the same product surface and focuses on reducing auth, balance, and support-diagnostic confusion seen after the previous release.
Highlights¶
- Expired sessions have a direct refresh path.
bullpen doctor auth --refresh --output jsonnow refreshes a refreshable session before reporting diagnostics, so wallet audit and support-bundle flows do not send users into a read-only diagnostic loop. - Read-only auth hints are more precise. Cached-auth paths now point to
doctor auth --refreshfirst and ask users to runbullpen loginonly when diagnostics say login is required. - Polymarket balance readback covers more preflight paths. The exact on-chain pUSD, USDC.e, and native-USDC fallback now also protects selected balance summaries and wrap/unwrap preflight guards when the portfolio service is temporarily unavailable.
- CLOB API-key support output is safer to share. Deposit-wallet CLOB binding
errors now separate support-safe diagnostics from the credential-bearing
reset-api-keyself-recovery command. - Deposit Wallet handling follows the current Polymarket path. The CLI now handles both older and newer Deposit Wallet addresses for checks and money-moving actions, so current accounts are not rejected just because their wallet differs from the older local address calculation.
- Deposit Wallet diagnostics explain their proof source.
bullpen doctor wallet, legacybullpen polymarket wallet check, andbullpen funds diagnose-depositcan now show whether the expected Deposit Wallet came from the current beacon path, the older UUPS path, or a degraded fallback when Polygon RPC was unavailable. - Relayer 5xx failures no longer encourage endless retries. Polymarket relayer/backend/provider failures now tell users and agents to wait, retry once, then stop and send the JSON output to support if the same failure repeats.
Still Limited¶
- This release does not add new product surfaces. It is a corrective release for auth diagnostics, balance readback, and support evidence.
- Account-specific wallet registry, Turnkey policy, dashboard-sync, repeated relayer/provider failures, and backend-owned repair states still require support or service-side action after the CLI captures current evidence.
- Solana remains experimental. Preview first and confirm balances before chaining live actions.
v0.1.111 - 2026-07-04¶
v0.1.111 is a focused stability follow-up to v0.1.110. It ships the fixes that were validated after the first v0.1.110 tag, mainly around balance readback and status output.
Highlights¶
- Polymarket balance readback is more reliable. When the portfolio service is temporarily unavailable, the CLI now falls back to exact on-chain reads for pUSD, USDC.e, and native USDC in wallet audit, pre-swap checks, and balance summaries.
- Funded wallets are less likely to look empty. A transient portfolio readback failure no longer turns a real pUSD balance into an unavailable or misleading zero-balance result.
- order-credit checks keep running. A pUSD readback failure no longer stops the CLI from checking off-chain order credit where that check is available.
- Auth status is easier to interpret.
bullpen status --output jsonnow separates a refreshable expired access token from a state that truly requires logging in again. - Wallet probe warnings are better scoped. Status output now marks whether a wallet probe warning affects the active trading wallet or only inactive residual wallets.
- Solana refresh retries are steadier. Balance refresh handles short transient timeouts with bounded retries while still refusing to replay authentication failures.
- Hyperliquid upstream failures are clearer. Retryable Hyperliquid provider 5xx responses now keep a typed provider-unavailable classification instead of looking like generic parse failures.
Still Limited¶
- This release does not add new product surfaces. It is a corrective release for the v0.1.110 stability work.
- Account-specific wallet registry, Turnkey policy, dashboard-sync, and backend-owned repair states still require support or service-side action.
- Solana remains experimental. Preview first and confirm balances before chaining live actions.
v0.1.110 - 2026-07-03¶
v0.1.110 is a stability and support-readiness release. It focuses on making money-moving failures easier to understand, closing several high-friction Polymarket cases, and keeping CLI output usable for agents and support.
Highlights¶
- Polymarket market buys retry bad tick-size reads. The CLI now reuses a recent tick size and retries once when Polymarket returns an unusable tick-size response during a market buy.
- Polymarket copy confirmations keep a usable market identity. When market metadata is sparse, pending copy executions now fall back to condition or token identifiers instead of showing a blank market.
- Wallet diagnostics are more precise. The CLI now separates normal self-service fixes from account states that need Bullpen-side repair, including relayer registry, selected-wallet, and CLOB readiness problems.
- Deposit-wallet CLOB binding errors are typed. Deposit Wallet accounts that cannot submit because their CLOB maker/API-key binding is stale now get a stable error class and next-step guidance.
- Device-login stalls fail clearly. If browser login completes but device polling does not finish, JSON output now returns a typed login-stalled diagnostic instead of a generic auth failure.
- Redeem support bundles include scan progress. Read-only redeem support output now records bounded scan progress and provider rate-limit context so support can distinguish incomplete scans from empty wallets.
- Managed same-chain wallet transfers are available. The CLI now supports the managed wallet-to-wallet transfer flow already used in the app, with the safest current scope focused on same-chain account movement.
- Solana live-swap cleanup is less brittle. Live Solana swap retries can respect rate-limit cooldowns, and cleanup sizing uses history-proven received amounts when available.
- Hyperliquid spot no-match errors are clearer. Spot IOC orders that simply do not match liquidity now get a specific no-match classification instead of looking like a generic execution failure.
- Polymarket API reads are more complete. Several lower-level Polymarket read and admin surfaces now have exact client adapters, giving future commands and support tools a more reliable base.
Still Limited¶
- Some wallet registry, selected-wallet, Turnkey policy, dashboard-sync, external-withdrawal, and copy-rejection details still require Bullpen support or service-side account data. v0.1.110 improves diagnosis and routing; it does not pretend those account states can always be repaired locally.
- Hyperliquid spot-copy execution remains gated until Bullpen can execute spot-copy orders end to end.
- Some new Polymarket connectivity work supports future commands, but is not a public command surface yet.
- Solana remains experimental. Use preview mode and confirm balances before chaining live actions.
v0.1.109 - 2026-07-01¶
v0.1.109 is a stability polish release. It focuses on clearer command results, safer retries, and better guardrails for agents and scripts.
Highlights¶
- Auth testing is stricter. The release proof harness now records cleaner auth-refresh evidence and avoids inherited debug settings that could hide a real version-gate problem.
- Funds diagnostics are clearer. Balance output now labels partially proven routing-wallet checks instead of making users infer whether every chain probe succeeded.
- Solana outputs are more consistent. Swap, limit-order, and DCA commands now use clearer success, signature, order, readback, and retry fields.
- Solana preview failures happen earlier. Unsupported Jupiter routes, under-minimum limit orders, invalid DCA cycle counts, and token-symbol mistakes are rejected before live submit when the CLI can detect them.
- Solana retry guidance is safer. Rate-limited Jupiter responses and delayed DCA/order indexing now include cooldown or readback guidance instead of encouraging blind retries.
- Hyperliquid errors are more actionable. Leverage caps, HIP-3 minimum order size, and spot minimum-notional failures now explain what blocked the command and what input to change.
- Hyperliquid order reads are easier to target.
bullpen hl orders [COIN]now accepts the same style of coin filter users already use for cleanup commands, including HIP-3 DEX-prefixed symbols. - TP/SL and Pear JSON are steadier for automation. TP/SL reads document the
canonical
legsoutput, and Pear open/copy-stop flows include clearer status and timestamp evidence. - Polymarket wrap and unwrap receipts are clearer. Live success output now includes stable success, transaction, and wallet provenance fields.
- Polymarket cancel workflows are safer. Cancel commands now reject obvious
missing-order placeholders such as
null,None,undefined, and empty comma segments before auth or network calls.
Still limited¶
- Solana remains experimental. Preview first and check balance/readback output before chaining live actions.
- HIP-3 writes remain selected-DEX operations, not all-DEX fanout.
- Pear and Hyperliquid copy trading remain bounded to the currently documented v1 surfaces.
v0.1.108 - 2026-06-29¶
v0.1.108 is a stability and parity polish release for Memes (Solana), Perps (Hyperliquid), and Prediction (Polymarket).
Highlights¶
- Memes is easier to operate from the CLI. Solana balance refreshes are clearer after swaps, token discovery has better filters, hidden tokens can be managed from the CLI, and history can be filtered by activity type.
- DCA on Solana is more complete. DCA commands now support price bands and scheduled starts, and DCA receipts explain when the service needs a short moment before a new or cancelled schedule appears everywhere.
- Solana swap receipts are safer. Swap output separates fixed SOL costs from the trade amount and warns when a fresh balance read has not caught up yet.
- Hyperliquid copy trading is more usable. Copy trading can be managed from the CLI, and leader lookup accepts the currently supported address or Bullpen username formats.
- Pear pair trading is clearer. The supported lifecycle is now documented: setup, status, positions, orders, open, close, cancel, risk update, and leverage update.
- HIP-3 trading is broader. The release was exercised across multiple HIP-3 markets instead of only the original SpaceX market, and account or margin rejections now explain what blocked the trade.
- Hyperliquid spot order cleanup is safer. Spot order reads, scale orders, and cancel-all flows now handle small test-sized workflows more predictably.
- Login, redeem, and rate-limit errors are clearer. Failed commands should point to the next diagnostic or retry step instead of asking users to guess.
- Old extra trading-key guidance was removed. Normal CLI trading uses the regular Bullpen login flow.
Still limited¶
- This release does not mean every web-app control is available in the CLI.
- Hyperliquid copy trading is experimental. Start small and check subscription state before unattended use.
- Pear support covers the current v1 lifecycle, not every advanced Pear screen.
- HIP-3 writes are single-DEX operations. Placing one write across every HIP-3 DEX at once is not available.
- Solana remains experimental. Use preview mode before live money movement.
v0.1.107 - 2026-06-24¶
v0.1.107 added the first broad Hyperliquid parity release line: HIP-3 trading, Pear pair trading, Hyperliquid copy trading, stronger auth recovery, and safer Solana previews.
Highlights¶
- Pear pair trading arrived in the CLI. Users can set up Pear, inspect pair state, open and close pairs, cancel orders, and adjust risk or leverage after opening a pair.
- Hyperliquid copy trading arrived in the CLI. Users can create, update, pause, resume, stop, and inspect copy-trading subscriptions, plus review risk settings and pending executions.
- HIP-3 single-DEX trading arrived. Users can open and close supported HIP-3 positions by naming the target DEX.
- Auth recovery became stricter. The CLI now avoids continuing when refreshed credentials cannot be saved safely, and several commands retry once after a recoverable expired-session response.
- Polymarket signing uses the active login context. Money-moving Polymarket paths now rely on the current Bullpen session instead of stale global state.
- Solana withdraw previews were added.
bullpen solana withdraw --previewshows the plan without signing or submitting a transaction. - Docs and skills were refreshed. Solana examples start with preview mode, and Solana remains clearly marked experimental.
Still limited¶
- Hyperliquid copy trading is experimental. Use small sizes and confirm the active subscription before leaving it unattended.
- Pear v1 does not include every advanced web-app control.
- HIP-3 all-DEX write fanout is not supported.
- Solana money movement remains experimental.
v0.1.106 - 2026-06-18¶
v0.1.106 focused on customer-facing Polymarket fixes, early Pear coverage, and release documentation cleanup.
Highlights¶
- Polymarket redeem improved for harder markets. The CLI can now find more redeemable positions when public market indexing is incomplete or the market uses a more complex payout structure.
- Portfolio valuation is clearer. Recoverable value is separated from stuck, resolved, or otherwise non-recoverable value instead of being blended into one misleading number.
- Funds and wallet refreshes are more stable. Balance reads and wallet rescans handle refreshable sessions and wallet selection more reliably.
- Solana DCA validation is clearer. Minimum-size failures now return a user-actionable validation error.
- Pear v1 started. The first Pear pair-trading commands were introduced for setup, reads, opening, closing, and cancelling within the supported v1 scope.
- Public docs were reorganized. Install, auth recovery, wallet routing, funds recovery, Hyperliquid, Pear, copy trading, and error-output docs were made easier to navigate.
Still limited¶
- Some Polymarket state-repair cases still need account-specific confirmation.
- Pear was still v1-only.
- Solana money movement was still experimental.
- This release did not claim complete Hyperliquid parity.
v0.1.105 - 2026-06-17¶
v0.1.105 was a small release focused on upgrade reliability and clearer unsupported-route errors.
Highlights¶
- Managed installs upgrade more reliably. Homebrew and npm installs now get package-manager-first upgrade guidance instead of being blocked by GitHub rate limits.
- TUI upgrade guidance is clearer. The terminal UI now points Homebrew and npm users to the right update path.
- Unsupported Polymarket withdraw routes fail clearly. The CLI now returns a clear unsupported-route error and directs users to the Bullpen web app when a route is not available in the CLI.
- Upgrade docs were improved. Homebrew trust and relink recovery steps were added for users who hit install friction.
Still limited¶
- This release did not add new trading surfaces.
- Larger Hyperliquid, Pear, and validation work moved to later releases.
v0.1.104 - 2026-06-16¶
v0.1.104 expanded Hyperliquid coverage and added Polymarket cleanup tools.
Highlights¶
- Hyperliquid sizing is clearer. Perp entry, close, take-profit, stop-loss, and modify flows now support explicit size units so users can avoid guessing whether a number is in USD or base size.
- Hyperliquid deposit dry-run is safer. Dry-run output makes clear that no signature or transfer was submitted.
- Hyperliquid DEX-scoped reads were added. Users can inspect markets, orderbooks, prices, funding, and candles for a specific DEX without signing.
- Pear pair trading v1 was introduced. The CLI added setup, login/logout, reads, open, close, close-all, cancel, and TWAP cancel commands.
- Polymarket resolved-position closeout was added. Users can preview resolved positions, redeem winning positions, and identify losing positions that have no payout.
- Wallet-routing repair became more explicit. Deposit-wallet repair commands now explain what they can and cannot prove.
- Hyperliquid spot lifecycle commands expanded. Spot order reads, fills, order history, and cancel commands were added or improved.
Still limited¶
- Pear was still v1-only.
- Some Hyperliquid live paths still required separate owner-approved testing.
- Full Hyperliquid parity was not claimed in this release.
v0.1.103¶
v0.1.103 focused on Polymarket redeem, split, and merge correctness, plus Hyperliquid spot and safety improvements.
Highlights¶
- Polymarket neg-risk redeem and merge became more reliable. The CLI now finds more held outcome tokens and includes the required approval step for neg-risk redemptions and merges.
- Polymarket split and merge use the same collateral path as production. This improves reliability across Safe, proxy, and deposit-wallet routes.
- Redeem commands use fewer RPC calls. The CLI narrows expensive scans to wallets that appear relevant before doing deeper checks.
- Redeem failures are safer. If a required on-chain scan cannot run, the CLI fails closed with a clear RPC hint instead of guessing.
- Hyperliquid spot reads and cancels were added. Users can inspect spot orders, order status, history, fills, and cancel resting spot orders.
- Hyperliquid safety checks improved. Fee checks, agent-wallet warnings, TP/SL previews, TWAP reads, vault/activity reads, and batch status reporting were hardened.
- Shipped files stopped leaking engineering labels. Confusing task labels were removed from shipped binaries and public docs.
Still limited¶
- Live spot buy and sell remained IOC-only at this point.
- Some Hyperliquid agent, TP/SL, spot, vault, and all-DEX write paths still needed more validation.
- Pear parity remained future work.
v0.1.102¶
v0.1.102 was a customer bugfix and triage release for Polymarket wallet routing, redeem diagnostics, trade previews, and support guidance.
Highlights¶
- Wallet routing fails safer. When the selected Polymarket wallet is ambiguous, money-moving commands fail instead of silently using a guessed wallet.
- Redeem dry-runs became clearer. Dry-run output now distinguishes possible candidates from proven live redeem readiness.
- Polymarket trade preview JSON became safer for agents. Preview output states that no signature was requested and no order was submitted.
- Order-not-filled errors became actionable. Liquidity misses now return a clear retryable error instead of a generic support escalation.
- Leaderboard and trader discovery output restored full wallet addresses when requested.
- Wrap and unwrap diagnostics improved. The CLI gives better context when a native-USDC or Safe call problem blocks wrapping.
- Support docs were expanded. Public docs now explain pUSD, Polygon USDC.e, native Polygon USDC, exchange deposit routes, cash-out boundaries, wrong network recovery, and support-owned cases.
Still limited¶
- Some wallet, KYC, bank, wrong-network, and missing-funds cases require support or web-app handling outside the CLI binary.
- This release did not claim broad Hyperliquid or Solana parity.
v0.1.101¶
v0.1.101 shipped the already-built Solana and Hyperliquid foundation work on top of the v0.1.100 customer hotfix.
Highlights¶
- Hyperliquid perps expanded. The CLI added stronger take-profit, stop-loss, scale, close-all, read-only account, order, and watch workflows.
- Hyperliquid TWAP commands were added. Users can create, cancel, list, and inspect TWAP activity.
- Hyperliquid minimum-size checks improved. Too-small orders are rejected earlier, before live submission.
- Hyperliquid spot and agent foundations were added. The release introduced spot pairs, spot orderbook, spot previews, IOC spot buy/sell, agent-wallet management, subaccounts, same-Hyperliquid USDC sends, account migration, and custom withdraw destination guards.
- HIP-3 account reads were added. Users can inspect account state across registered DEXes with explicit flags.
- Solana support expanded. Token search, holders, recent traders, limit orders, DCA, stats, closed positions, and withdraw fallback workflows were added or polished.
- Docs, skills, and preview-safety tests were refreshed.
Still limited¶
- This was not complete Hyperliquid parity.
- Solana live money movement remained experimental.
- Some deeper auth-refresh and Windows locking work remained follow-up scope.
v0.1.100¶
v0.1.100 was a customer hotfix release focused on Polymarket trading, wallet diagnostics, and auth stability.
Highlights¶
- Login-backed trading became more stable. Polymarket trading paths refresh sessions more consistently after auth checks.
- Forced logout can recover missing local credential salt.
bullpen logout --forcecan clear broken local credentials so users can log in again. - Intact local signing keys can keep working during temporary readiness issues. The CLI avoids unnecessary failure when local signing material is still present and valid.
- Neg-risk redeem detection improved.
redeem-neg-riskdetects more index-set layouts, including multi-index neg-risk positions. - Wrapped POL / WMATIC sweeps improved. The CLI can fall back to direct wrapped-token balance reads when portfolio data omits the token row.
- Buy previews account for full cost more accurately. Preflight balance checks better match the submitted order cost.
- Sell-max explains unsellable dust.
sell --maxnow warns when a tiny residual share amount cannot be sold. - Wallet-routing checks were hardened. Polymarket money-moving commands use stricter selected-wallet checks before submitting.
Still limited¶
- This release did not repair server-side account damage, deleted local signing keys, KYC issues, wrong-chain deposits, bank settlement issues, or web/mobile bugs.
- Remaining CLI-vs-web redeem discrepancies still needed fresh reproduction details.