Configuration
الإعدادات
Start with meaning, then move to detail.
This lesson explains Configuration 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 Directory Structure, Managing Configuration, Configuration Precedence, then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand Configuration 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.
Configure Hermes Agent — config.yaml, providers, models, API keys, and more
What does the source say, and in what order?
- 01Directory Structure
Start here to understand the core idea or structure.
- 02Managing Configuration
Read this after the foundation, then connect it to the previous step.
- 03Configuration Precedence
Read this after the foundation, then connect it to the previous step.
- 04Environment Variable Substitution
Read this after the foundation, then connect it to the previous step.
- 05Provider Timeouts
Read this after the foundation, then connect it to the previous step.
- 06Update Behavior
Read this after the foundation, then connect it to the previous step.
- 07Terminal Backend Configuration
Read this after the foundation, then connect it to the previous step.
- 08Backend Overview
Read this after the foundation, then connect it to the previous step.
- 09Local Backend
Read this after the foundation, then connect it to the previous step.
- 10terminal.homemode
Finish here to verify the result and special cases.
Copy only after you understand the effect.
~/.hermes/
├── config.yaml # Settings (model, terminal, TTS, compression, etc.)
├── .env # API keys and secrets
├── auth.json # OAuth provider credentials (Nous Portal, etc.)
├── SOUL.md # Primary agent identity (slot #1 in system prompt)
├── memories/ # Persistent memory (MEMORY.md, USER.md)
├── skills/ # Agent-created skills (managed via skill_manage tool)
├── cron/ # Scheduled jobs
├── sessions/ # Gateway sessions
└── logs/ # Logs (errors.log, gateway.log — secrets auto-redacted)hermes config # View current configuration
hermes config edit # Open config.yaml in your editor
hermes config get KEY # Print a resolved value
hermes config set KEY VAL # Set a specific value
hermes config unset KEY # Remove a user-set value
hermes config check # Check for missing options (after updates)
hermes config migrate # Interactively add missing options
# Examples:
hermes config get model
hermes config set model anthropic/claude-opus-4
hermes config set terminal.backend docker
hermes config unset terminal.backend
hermes config set OPENROUTER_Aauxiliary:
vision:
api_key: ${GOOGLE_API_KEY}
base_url: ${CUSTOM_VISION_URL}
delegation:
api_key: ${DELEGATION_KEY}Read 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.