Profile
- Tune session timeout/expiry early — Use configuration docs to adjust session retention for slower-moving threads so context is kept when needed.
Signals
Listed in the awesome-hermes-agent README
Sources: 2 / Surfaces: 1
What the upstream surface says
Short excerpt only, so you can decide whether to click out.
Configuration | Hermes Agent Skip to main content Hermes Agent Docs Skills Home GitHub Discord Getting Started Using Hermes CLI Interface TUI Configuration Sessions Profiles: Running Multiple Agents Git Worktrees Docker Security Checkpoints & Rollback Features Messaging Platforms Integrations Guides & Tutorials Developer Guide Reference Using Hermes Configuration On this page Configuration All settings are stored in the ~/.hermes/ directory for easy access.
Directory Structure ~/.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 skillmanage tool) ├── cron/ # Scheduled jobs ├── sessions/ # Gateway sessions └── logs/ # Logs (errors.log, gateway.log — secrets auto-redacted) Managing Configuration hermes config # View current configuration hermes config edit # Open config.yaml in your editor hermes config set KEY VAL # Set a specific value hermes config check # Check for missing options (after updates) hermes config migrate # Interactively add missing options # Examples: hermes config set model anthropic/claude-opus-4 hermes config set terminal.backend docker hermes config set OPENROUTERAPIKEY sk-or- ..
# Saves to .env tip The hermes config set command automatically routes values to the right file — API keys are saved to .env , everything else to config.yaml .