Skip to main content
Condor’s Telegram bot lets you control your trading setup from your phone. You can chat with it in plain words, or use commands.

Getting access

The first time you send /start, Condor registers you as pending and replies Access Request Submitted with your user ID and username. The admin gets a New Access Request message. The admin approves or rejects you from /admin → 👥 Pending Requests (or from the Workspace’s Settings → Admin). Until then, /start replies Access Pending. A blocked user gets Access denied. Once you’re approved, /start replies:
It’s a plain message, not a menu. Despite what it says, /keys only lists your keys. You add them in the Workspace. See Exchange credentials are Workspace-only below.

Chatting with Condor

Any message that isn’t a command, or an answer to a prompt Condor is waiting for, goes to the assistant. If no session is running, one starts. Ask in plain words, for example:
  • “What’s my balance on Binance?”
  • “Which analysis routines do I have?”
  • “Run technical analysis on BTC-USDT”
Condor answers using its tools: it reads your portfolio, runs routines such as technical_analysis, and can create executors. Actions that trade ask you to approve them first.

Commands

Everyone sees these in Telegram’s command menu: The admin also sees: /swap also works. It opens the same menu as /trade but isn’t listed in the command menu.

/portfolio

Shows a summary for your active server: the total value, then each connector’s total and its tokens worth $1 or more. Buttons open each connector’s full list, and 🔄 Refresh re-fetches balances from the exchanges. There are no PnL periods or charts in Telegram. For those, use the Workspace’s Portfolio page. See Seeing Your Portfolio.

/bots

Opens the Bots Dashboard for your active server, with one button per running bot, 📜 Historical for past bots, 🔄 Refresh and ❌ Close. Tapping a bot shows:
  • Its status and uptime
  • Each controller with its PnL and volume, and a quick start/stop button
  • A count of recent errors
  • 📋 Logs and 🛑 Stop Bot
Tapping a controller shows its config, which you can edit by sending key=value. Its buttons depend on the controller type: ▶️ Start / 🛑 Stop, plus 📊 Chart for grid strike controllers or 📋 Clone for PMM Mister. To create a bot, use /new_bot.

/agent

Opens the assistant menu. It shows who you’re talking to, the LLM, and whether the session is ready or busy. With an active session: With no session, the menu offers Start, Change LLM, Talk to, Conversations and Close. /agent <name> goes straight to an agent without the menu, for example /agent orca_lp_expert. A partial name works if it matches only one agent. /agent condor goes back to the coordinator.
/stop only stops the reply being written; the session and its context stay. The ⏹ Stop generating button under a streaming reply does the same. End session ends the conversation. Neither one stops an agent’s running loop. See Agent Loops.
The agent only works in private chats.

/executors

Lists your running executors, with buttons to create a grid or position executor, view an executor’s details and stop it, and page through history. Other executor types are created from the Workspace’s Trade page or by the assistant.

/trade

One menu for CEX and DEX venues. Pick the venue and pair, set side, amount and order type with buttons, then tap Quote and ✅ Execute. Type an amount like $100 to size it in USD. On a CEX you can also view and cancel 📋 Orders, view and close 📊 Positions, and set leverage and position mode on perpetual venues. /swap is an alias.

/lp

The liquidity menu: 💱 Swap and 💧 Liquidity Pools. From there you can browse Meteora, Orca and GeckoTerminal pools, open a position, view your positions, collect fees (from one position or with 🎁 Collect All) and close positions.

/servers, /keys, /gateway - System Configuration

Configuration is split across three commands:

Exchange credentials are Workspace-only

/keys only lists the exchanges that are connected. To connect or remove one, use the Workspace under Settings → Keys and Wallets. The /keys reply includes a login link to that page, valid for 5 minutes. This way an API secret is never typed into a Telegram chat, where it would stay in message history on Telegram’s servers. See Exchange Credentials.
When creating the key at your exchange, enable read + trade only. Do not enable withdrawal or transfer permissions.
Older material refers to a single /config command. It no longer exists. Use the three commands above, or the Workspace’s Settings page, which covers the same ground in one place.

/update - Updates and Restart

Admin only. Checks Condor and the Hummingbot API beside it, showing what each is running and what is available — for the API, both its git checkout and its container image, since they answer different questions. Before anything runs, a preflight reports blockers (a diverged checkout, local changes that would be overwritten, an unreachable registry) with a way out where one exists — a dirty checkout offers discard or stash — and warnings that never refuse, such as restarting the API reaping its executors. An update lands the code, syncs dependencies and rebuilds the Workspace, then waits for you to restart, because the moment is yours (bots may be trading). Tap Restart Now when you are ready, or run make restart. See The restart step.
The Workspace has the same panel at Settings → Updates, over the same engine — an update started here can be watched to completion there, and a Local mode install uses that panel instead of this command. See Keeping Condor updated.

/cancel - Back Out of a Flow

Several flows ask for the next message as their answer — a server name, a price, an amount. /cancel abandons that flow and returns you to normal command handling. It is what the prompts themselves tell you to send, and it works from inside any of them.

Notifications

Condor messages you when background work finishes:
  • A delegated task completes
  • A routine run ends
  • An agent sends you a notification
  • System notices, such as runs that a restart interrupted
The same notices also appear under the bell in the Workspace.

Voice messages

Send a voice message instead of typing. Condor transcribes it locally with Whisper (no audio leaves your server), shows you the text, and sends it to the assistant. You choose the Whisper model and language in the Workspace under Settings → Voice & AI. The default model is small; options run from tiny (fastest) to large-v3 (most accurate). Language is auto-detected unless you set one. Condor loads the default model at startup. A different model is downloaded the first time you use it, so that voice message takes longer.

Security

  • Access approval: new users must be approved by the admin before Condor responds to them. See Getting access.
  • No secrets in chat: exchange keys are added in the Workspace, not Telegram.
  • Separate sessions: each chat has its own assistant session.
Using Condor in Telegram every day? Tell us what’s working and what you wish it could do.

Help shape Condor

What’s working? What’s confusing? What do you wish Condor could do? Your answers go straight to the Hummingbot Foundation team and directly shape what we build next.