Skip to main content
The Bots page manages long-running, containerized Hummingbot bots โ€” always-on strategies with no LLM in the loop. Five tabs cover a botโ€™s whole life: Active, Runs, Editor, Backtest, and Archived.

Active

Live bots, with a stat strip for total PNL, volume, active bot count, and running controllers. Deploy Bot launches a new bot from a controller config.
The Active tab: stat strip and Deploy Bot

Runs

Every bot run, past and present: status (Deployed or Archived), PNL, volume, start time, and duration. This is the audit trail โ€” click a run to inspect its performance.
The Runs tab: bot run history with PNL and duration

Editor

A code editor for the strategy files on the server: Controllers (.py, grouped into directional trading, market making, and generic) and their Configs (.yml). Edit in the browser, save to the server, and the next deploy uses your version. New files and uploads happen from the explorer header.
The Editor tab: controller and config file explorer

Backtest

Replay a controller config against historical candles before it touches capital: pick the config, a time range (1D/1W/1M/3M presets), candle resolution, and a trade cost, then Run Backtest. Runs land in the Tasks list with their results.
The Backtest tab: config, time range, resolution, and trade cost

Archived

Stopped bots whose databases were archived โ€” each card shows its trades and orders, and opens into the full performance breakdown.
The Archived tab: archived bot run cards

Using Telegram

/bots lists active bots with real-time status and metrics; each bot opens into ๐Ÿ“‹ Logs, ๐Ÿ“Š Chart, and ๐Ÿ›‘ Stop Bot, with ๐Ÿ“œ Historical for past runs (stop-and-archive included). /new_bot walks through creating a bot configuration from a controller.

Learn more