Hermes Core
Freshness check
Before writing or changing any Hermes config, run hermes --version and
hermes update --check, then read
https://github.com/NousResearch/hermes-agent/releases/latest. If the installed
or latest version is newer than 0.23.0, read every release note since 0.23.0
("Upgrade notes" first) and adjust. Never apply guidance from this skill to a
newer version without that check.
Decision map
| Question | Load |
|---|---|
| Install, first setup, update, channels, rollback | install-update.md |
| Several agents on one machine, gateway processes | profiles-gateway.md |
Which config.yaml key, default, precedence, hermes config |
config-schema.md |
| Choosing a model / provider / fallback / reasoning effort | models-providers.md |
| SOUL.md vs .hermes.md vs AGENTS.md, lookup order | persona-context-files.md |
Fresh context, /new, session pruning, prompt refresh |
sessions-and-context.md |
| Something is broken: logs, doctor, status | logs-health.md |
| Is there a newer Hermes? What changed? | release-watch.md |
| Ready-to-fill files | templates/ |
Critical rules
- Never invent a key. Write only keys found in
cli-config.yaml.example,user-guide/configuration.mdor the source. Afterhermes config set, runhermes config get <key>: it prints a stderr notice when Hermes may not read the key. - Secrets go in
.env, never inconfig.yaml.hermes config setroutes everyUPPER_SNAKEname to.envautomatically. - One profile = one Hermes home. Two agent processes must not share one
home; one profile per agent, deployed as a distribution
(
hermes profile install <dir> --name <name> --yes --force, hermes-deploy). - Profiles are not sandboxes. Set an absolute
terminal.cwdper profile for a predictable workspace; isolation belongs to hermes-security. - Fresh context is not automatic. Idle/daily
session_resetis ignored by core since v0.22.0; use/newor the catalog pluginhermes-session-reset-policy. - SOUL.md lives only in
HERMES_HOME; project rules live in.hermes.md(walks up to the git root). Cron jobs load project rules only with--workdir(see hermes-cron). - Docs disagree with code on some defaults (e.g. delegation limits,
sessions.auto_prune). When two official sources disagree, set the value explicitly instead of relying on the default.
Minimal setup sequence
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash # Linux/macOS/WSL2
source ~/.bashrc # or ~/.zshrc
hermes setup # full wizard (or: hermes model, hermes tools, hermes gateway setup)
hermes doctor # exit 1 while a problem remains
hermes --version
Then edit config from templates/config-core.yaml
with hermes config edit, and validate with hermes config check + hermes doctor.
Sources
- https://github.com/NousResearch/hermes-agent
- https://hermes-agent.nousresearch.com/docs/getting-started/installation
- https://hermes-agent.nousresearch.com/docs/getting-started/updating
- https://hermes-agent.nousresearch.com/docs/user-guide/configuration
- https://hermes-agent.nousresearch.com/docs/user-guide/profiles
- https://hermes-agent.nousresearch.com/docs/user-guide/features/context-files
- https://hermes-agent.nousresearch.com/docs/user-guide/messaging/ (Session continuity)
- https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.0