Skip to content

Run

Live algorithm execution, wallets, monitoring, and management

This is where your algorithm moves from testing to the real market. Run lets you choose an algorithm, select a funded run wallet, set live execution limits, complete approvals, and monitor the run while it trades.

For a hands-on first live run, see the Run Walkthrough →

On this page: Going Live · Run Wallets · Launch Settings · Monitoring · Run States · Stopping and Restarting · Tuning a Live Strategy


Make sure you’ve done these before switching to live:

  • Backtested on at least 6 months of data
  • Checked that your Sharpe ratio is above 1.0 and max drawdown is acceptable
  • Ideally run rolling cross-validation to confirm the strategy generalizes
  • Chosen a conservative live capital amount
  • Created and funded a dedicated run wallet

Switch to Run mode using the header mode selector. Select an algorithm, select a funded wallet, configure your live settings, and click Start Run.

The launcher will guide you through any required wallet or builder fee approvals before the run starts.


Run uses dedicated wallets so live algorithms are separated from regular trading.

Before starting a run:

  • Choose or create a run wallet
  • Fund the wallet
  • Make sure the wallet is not already being used by another active run
  • Complete any required approvals in the launcher

SettingDescription
AlgorithmSaved algorithm and version to run live
Run WalletFunded wallet used by this live run
SymbolMarket the algorithm trades
CapitalLive capital limit for the run
LeverageLeverage used by the strategy
Trades LimitMaximum number of trades before the run stops
Assume Position NowStarts as if the strategy is already in a position
Close Position on ExitAllows the run to close positions when exit logic fires
Session Calendar PolicyPause behavior around configured session windows
Reset / Follow-Up ChainControls cooldown and follow-up behavior after resets

Pay close attention during the first day of a live run. Here’s what to watch:

  • Fill prices — are entries and exits landing close to where the test expected them? Some slippage is normal, but consistent deviation may mean your order type or timeframe needs adjusting.
  • Trade frequency — is the algorithm trading as often as the test predicted? If it’s much more or less active, market conditions may have shifted.
  • Drawdown — if your live drawdown exceeds your test’s max drawdown early, consider pausing to investigate.

Run mode gives you dedicated monitoring panels:

  • Run Wallets — create, fund, and select wallets for live runs
  • Run Configuration — select the algorithm, wallet, market, capital, leverage, limits, and session behavior
  • Run Info — active runs, run history, positions, orders, trades, details, and config
  • Run Metrics — summary, chart, equity curve, and performance details

Use the MCP agent tools for programmatic monitoring:

ToolWhat It Shows
list_runsAll runs with status, filtered by algoId or status
get_backtest_resultsMetrics for a completed run
get_account_overviewAccount snapshot including active positions and running algos

StateWhat It Means
NEWRun created, initializing
RUNNINGActively executing — watching the market and placing trades
STOPPINGStop requested, winding down gracefully
STOPPEDYou (or the system) paused the algorithm. Open positions remain unless you close them
DONERun completed normally
FAILEDRun encountered an error
CANCELLEDThe run was aborted before completion

You’ll typically see RUNNING after the run starts. If something looks off, you can stop it at any time.


Click Stop from Run mode or ask the agent:

"Stop my running algorithm"

The run moves to STOPPING while it winds down, then settles into a stopped state.

  1. Stop the current run
  2. Switch to Build mode and edit the algorithm (creates a new version)
  3. Switch to Test mode and backtest the new version to validate changes
  4. Switch to Run mode and start the updated version

  • Live Sharpe is significantly below test Sharpe — the strategy may be overfit to historical data
  • Drawdowns are larger than expected — risk parameters may need tightening
  • Trade frequency has dropped off — the market regime may have shifted away from your strategy’s edge
  • Most exits are stop losses — entry timing or stop placement may need work

Based on live performance, go back and tweak:

  • Thresholds — if signals trigger too frequently or rarely
  • Indicators — swap underperforming indicators (check usefulness scores from tests)
  • Position sizing — reduce if drawdowns are too large
  • Stop loss — tighten or loosen; experiment with trailing stops

If the market regime shifts, test and validate the strategy again on recent data:

  1. Run a backtest on recent data to see current performance
  2. Adjust the algorithm in Build if metrics have degraded
  3. Validate with rolling cross-validation in Test
  4. Start a small live run with the updated version

See Test → Optimize for the validation workflow.


Want to…Go to
Set up autonomous AI tradingAgent Features →
Validate your strategyTest Features →
Walk through your first runRun Walkthrough →