Environment Variables
Environment Variables
Start with meaning, then move to detail.
This lesson explains Environment Variables as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect LLM Providers, Provider Auth (OAuth), Tool APIs, then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand Environment Variables without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Provider
- The service that runs or provides access and authentication to a model.
- Gateway
- The process that connects Hermes to channels such as Telegram or Discord and routes messages.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
- Tool
- A structured action the agent can call to read or change something.
Complete reference of all environment variables used by Hermes Agent
What does the source say, and in what order?
- 01LLM Providers
Start here to understand the core idea or structure.
- 02Provider Auth (OAuth)
Read this after the foundation, then connect it to the previous step.
- 03Tool APIs
Read this after the foundation, then connect it to the previous step.
- 04Skill API Keys
Read this after the foundation, then connect it to the previous step.
- 05Langfuse Observability
Read this after the foundation, then connect it to the previous step.
- 06Nous Tool Gateway
Read this after the foundation, then connect it to the previous step.
- 07Terminal Backend
Read this after the foundation, then connect it to the previous step.
- 08SSH Backend
Read this after the foundation, then connect it to the previous step.
- 09Container Resources (Docker, Singularity, Modal, Daytona)
Read this after the foundation, then connect it to the previous step.
- 10Persistent Shell
Finish here to verify the result and special cases.
Copy only after you understand the effect.
export HERMES_WRITE_SAFE_ROOT=/path/to/project:/home/you/.hermescompression:
enabled: true
threshold: 0.50
target_ratio: 0.20 # fraction of threshold to preserve as recent tail
protect_last_n: 20 # minimum recent messages to keep uncompressedfallback_providers:
- provider: openrouter
model: anthropic/claude-sonnet-4Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.