Bots vs Executors
When to Use Bots
Bot Lifecycle
Creation
A bot runs one or more saved controller configs. Create the configs first (see Controllers), then deploy a bot that runs them. Workspace: on the Bots page, click Deploy bot, select one or more configs, and click Deploy. Telegram: send/new_bot, select one or more configs, choose 🚀 Deploy, and answer the prompts for instance name, credentials profile, drawdown limits and image. Telegram lists configs for grid_strike, pmm_mister and pmm_v1 only.
API: deploy a bot from existing controller config files (without .yml). Pass several configs to run multiple controllers in one bot:
instance_name, so the bot (and its Docker container) is named like my-market-maker-20261015-143000. The response returns the full name as unique_instance_name. Use that name in every later call.
Starting and Stopping
Start and stop work at two levels. A single controller pauses or resumes one strategy while the rest of the bot keeps running. Stopping a controller turns on its kill switch: it cancels its orders and stops opening new executors, but keeps its config.- Workspace: select the controller on the Bots page and click Pause or Start.
- Telegram:
/bots→ select the bot → tap ⏸ or ▶️ next to the controller, or open the controller and use Stop / Start.
- Workspace: select the bot and click Stop bot, then Confirm.
- Telegram:
/bots→ select the bot → 🛑 Stop Bot → ✅ Yes, Stop.
Monitoring
Workspace: the Bots page shows PnL, volume, win rate, open positions and executors for any bot, controller or group. Finished runs are under Terminated. Telegram:/bots lists running bots. Open one for its controllers and recent errors.
API:
/bot-orchestration/controller-performance-history (see Monitoring Controllers). The Bots page charts the same history.
Logs
- Workspace: select the bot and click Logs.
- Telegram:
/bots→ select the bot → 📋 Logs.
Container Isolation
Each bot runs in an isolated Docker container:- Separate filesystem
- Own log stream
- Can be stopped individually
Integration with Agents
Agents deploy and manage bots with themanage_bots tool. It takes an action: deploy, status, logs, stop_bot, start_controllers, stop_controllers, get_config or update_config.
deployneedsbot_nameandcontrollers_config. Optionalmax_global_drawdown_quote,max_controller_drawdown_quote,account_nameandimagematch the Workspace’s advanced settings.statustakes no other arguments and reports every active bot.stop_botstops the bot and archives it.start_controllers/stop_controllersneedbot_nameandcontroller_names.update_configchanges a running controller’s config (bot_name,config_name,config_data).
manage_controllers (list, describe, upsert, delete).
An agent can also carry its own controllers in its folder and push them to the server when it needs them. See Agent architecture → Controllers and, for a worked example, Guide: Market Making Expert Agent.
