.env holds the settings below, and
config.yml holds servers, users, permissions, preferences and chat defaults — written
by make setup and by /servers, not by hand.
Almost nothing here needs setting. The install wizard writes what a working
install requires, and the rest exist for operators with a specific reason.
After editing
.env, restart Condor for it to take effect — make restart.
make doctor re-reads it and reports what the running install would see.Identity and mode
Workspace
Privacy
Both are the operator-level kill switches. They override anything chosen in the Workspace, and neither needs to be set on a fresh install — see Privacy: telemetry and sharing.Updates
AI models
How to choose and set up a model is covered in LLM Integration. These are the variables it uses:Market data
Retention and limits
Every one of these has a working default. They exist for installs where disk, history depth or context size needs a different answer.Storage locations
Where Condor keeps agents and runtime data. Each defaults to a folder inside your Condor install. See Architecture for how the two agent folders are merged.Timeouts
Every deadline has a default that suits most installs. Override one withCONDOR_TIMEOUT_<NAME>, in seconds. A value that is not a number is ignored, with a warning in the log.
Advanced
Rarely set, and listed so a value you find in someone’s.env is not a mystery.
Environment overrides
Condor reads.env at startup, but a variable already set in the environment it starts from takes priority. That usually happens by accident. For example, a tmux server started from another project hands its own TELEGRAM_TOKEN to every window, and Condor then runs as that project’s bot.
At startup, Condor logs a warning for each .env variable that the environment overrides. It names the variable, never the value. For TELEGRAM_TOKEN it also names both bot ids. To let .env win, start Condor where the variable is unset: unset TELEGRAM_TOKEN, or tmux set-environment -gu TELEGRAM_TOKEN for new tmux windows.
Not in .env
Servers, their credentials, users, roles and per-chat defaults live in
config.yml, written by make setup and by /servers. The Hummingbot API’s
own settings — API_BIND, DB_BIND, broker credentials, GATEWAY_PASSPHRASE —
live in hummingbot-api/.env, not here.
