Skip to main content
New to Condor, or picking up where you left off? Find the route to what you want to do. You don’t need to read every page in order.

​
By experience level

Each level builds on the one before it.
Get Condor running on your own machine with no Telegram account, and build one Condor Agent from the browser.
1

Install locally

Installing → Local
2

Open the Workspace

Workspace
3

Connect an exchange

Credentials
4

Build an agent

Build Your First Agent

​
Which install do you want?

All three run the same agents, bots, routines and Workspace. What differs is who can reach them and where alerts go. Most people start local and move up, and re-running make setup switches mode at any time.

Local

Best for trying it out. Nothing extra needed.

Local + Telegram alerts

Best for most people. Needs a bot token and your Telegram user id.

Server

Best for anything holding real capital. Needs Tailscale too.
Local mode has no login. Whoever reaches the port has full trading control, so it only listens on 127.0.0.1. See Choose your install for the full comparison, and Start local, grow later for each hop. Add Telegram early, because a Local install’s agent history stays behind when you do.

​
What do you want Condor to do?

Condor gives you four ways to execute a trade, from fully autonomous to fully manual. Most people end up combining more than one.

Condor Agent

Decides: an LLM, reasoning every tick.
Runs: long-running and adaptive.
Best for: an AI-assisted strategy that adapts to conditions.

Bot

Decides: a script or controller with fixed logic.
Runs: long-running and fixed.
Best for: always-on market making or grid trading without AI in the loop.

Executor

Decides: you, or an agent, one shot.
Runs: short-lived, a single operation.
Best for: a single trade, or a stop-loss and take-profit.

Routine

Decides: deterministic Python.
Runs: on a schedule or a trigger.
Best for: reports, alerts and indicators without LLM cost.

​
By use case

Installing (local install—Tailscale not required; Local mode skips Telegram entirely) → Credentials → dry-run an agent in Build Your First Agent
Installing (remote install—Tailscale required) → Servers → Agent Loops
Condor Agents Architecture (multi-agent via controller_id) → Global Routines → Servers

​
Key features

What Condor does, and where each feature is documented.

​
Something not working?

Run make doctor from the Condor directory. It is read-only, checks your setup end to end, and names the fix for each problem it finds. For anything it doesn’t cover, see Troubleshooting.

​
Next steps

Introduction

What Condor is and who it’s for

Motivation

Why Condor is architected this way

GitHub

Source code and issues

Give Feedback

2-minute survey that shapes the roadmap

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.