Hermes · Env Var Cheat Sheet
One file, predictable names. Learn the patterns and you can guess any variable you need.
The reference lists 200+ variables, but you never read it cover to cover. They all go in one file, ~/.hermes/.env, or set them with hermes config set VAR value (secrets auto-route there). The reference is just five buckets: LLM Providers, Tool APIs (search, STT/TTS, browser), Terminal (TERMINAL_*), Messaging (every chat platform), and Hermes internals (HERMES_*). And the names are predictable: a provider key is <PROVIDER>_API_KEY, override its endpoint with <PROVIDER>_BASE_URL, connect a chat platform with <PLATFORM>_BOT_TOKEN, gate access with <PLATFORM>_ALLOWED_USERS, and Hermes' own knobs start with HERMES_. Realistically you'll only set a handful: a provider key, a bot token + allowlist, HERMES_HOME, and HERMES_TIMEZONE.
Sources · What this video distills
1 docs page · every command below traces to one of themCommands shown · Copy and paste
each shows the source doc it came fromhermes config set OPENROUTER_API_KEY sk-or-...hermes config set TELEGRAM_BOT_TOKEN ... · hermes config set TELEGRAM_ALLOWED_USERS 12345,67890export HERMES_HOME=~/.hermes-work · hermes config set HERMES_TIMEZONE America/New_York