Bots vs Executors
When to Use Bots
Bot Lifecycle
Creation
Create a bot via Telegram or API: Telegram:.yml). Pass several configs to run multiple controllers in one bot:
Starting and Stopping
Telegram:Monitoring
Telegram:/bots shows:
- Bot status (running/stopped)
- Uptime and resource usage
- Recent P&L
- Active orders and positions
/bot-orchestration/controller-performance-history (see Monitoring Controllers), or view it in Condor under Bots → Runs. When a bot runs multiple controllers, Bots → Active charts their combined P&L with toggles to isolate each one.
Logs
Telegram:Container Isolation
Each bot runs in an isolated Docker container:- Separate filesystem
- Independent network
- Own log streams
- Can be started/stopped individually
Integration with Agents
Agents can deploy and manage bots programmatically: Themanage_bots MCP tool handles the full lifecycle through a single action parameter (deploy, status, logs, stop_bot, start_controllers, stop_controllers, get_config, update_config):

