Skip to main content
The Workspace is Condor’s browser interface. You chat with Condor and its agents, check your portfolio, trade, manage bots and routines, and configure the install.
The Condor Workspace home: the Agents · Portfolio · Trade · DEX · Bots · Routines · Settings tabs across the top and a chat answering How is my portfolio doing?

Open the Workspace

Open the Workspace on the machine running Condor:
There is no login step. The Workspace signs you in as ADMIN_USER_ID. Local mode only listens on 127.0.0.1, so you can’t reach it from another machine. See Local for details.
If the server selected in the top bar has no exchange keys yet, every page except Agents, Routines and Settings shows a prompt to connect keys. See Exchange Credentials.

The pages

The top bar has seven tabs: Agents · Portfolio · Trade · DEX · Bots · Routines · Settings. On the right are the server selector, the display currency, the notification bell, Report an issue and the theme switch. Each agent also has its own page at /agents/<slug>, where you run and watch its loops. See Agent Loops. On every page except Agents, a chat button in the bottom-right corner opens a quick chat about the page you’re on. The theme switch cycles through dark, light and a color-blind mode. Your browser remembers the choice.

Keyboard shortcuts

Telegram and the Workspace

Condor’s Workspace and Telegram bot run in the same process and share the same data: servers, agents, conversations, routines and preferences. Conversations started in Telegram appear in the Workspace’s conversation list with a Telegram tag. /update in Telegram and Settings → Updates run the same update.

Change the Workspace address

By default the Workspace runs at http://localhost:8088. Two settings in Condor’s .env control it:
  • WEB_URL: the address Condor puts in /web links. It also sets the port Condor listens on, and it takes priority over WEB_PORT. If WEB_URL has no port, Condor listens on port 80 for http:// or 443 for https://.
  • WEB_PORT: the port, used only when WEB_URL is not set.
For example, to reach the Workspace at a server’s IP in Telegram mode:
Then restart Condor with make restart and send /web for a link with the new address.
Because WEB_URL sets the listening port, you can’t point it at a reverse proxy address without a port. For example, WEB_URL=https://dashboard.example.com makes Condor itself try to listen on port 443, where the proxy already is. If you use a proxy, either include a port in WEB_URL that the proxy also serves on, or accept that /web links will show Condor’s own address and port.
Where the Workspace listens depends on the mode: WEB_HOST overrides all of these. See What binds where by default.
Local mode has no login. Don’t set WEB_HOST to expose a Local mode Workspace to a network.

Tech stack

The Workspace is a React 19 single-page app built with Vite and TypeScript, styled with Tailwind CSS 4. It uses TanStack Query for data, lightweight-charts and Recharts for charts, and CodeMirror for the config editor. Condor serves it from the same process as the Telegram bot.

Next step

Talk to your agents

Learn the chat workspace, the Agent panel and how approvals work