tentaflake: Skill for Claude Code

Hermes Config Manager

Tentaflake context: In this repo, agents are defined declaratively in my-agents.nix via the settings attribute on mkHermesAgent. When settings is set, the resulting config.yaml is mounted read-only inside the container — interactive hermes config set changes won't persist across restarts. Use my-agents.nix.example as your reference for the declarative approach. API keys belong in /run/secrets/hermes-<name>.env. This skill is still useful as an in-container reference for Hermes' native config options and for troubleshooting inside a running agent.

When to Use

• Set up or modify Hermes agent configuration
• Switch terminal backends (local/docker/ssh/modal/daytona/singularity)
• Configure model provider and API keys
• Manage profiles
• Migrate config after update
• Debug config issues
• Enable/disable toolsets globally

Procedure

1. Directory Structure

~/.hermes/
├── config.yaml     # Settings — model, terminal, TTS, compression
├── .env            # API keys and secrets (chmod 600)
├── auth.json       # OAuth provider credentials
├── SOUL.md         # Agent identity (slot #1 in system prompt)
├── memories/       # MEMORY.md, USER.md
├── skills/         # Agent skills
├── cron/           # Scheduled jobs
├── sessions/       # Gateway sessions
└── logs/           # errors.log, gateway.log

2. Key Commands

hermes config              # View current config
hermes config edit         # Open in $EDITOR
hermes config set KEY VAL  # Set value (API keys → .env, rest → config.yaml)
hermes config check        # Find missing options after update
hermes config migrate      # Interactively add missing options
hermes config show         # Display full config

hermes config set auto-routes: API keys → .env, everything else → config.yaml.

3. Config Precedence

Settings resolved in order (highest first):

1. CLI args (hermes chat --model X)
2. ~/.hermes/config.yaml
3. ~/.hermes/.env (fallback for env vars)
4. Built-in hardcoded defaults