Soul pack
Write identity into Hermes home. Keep project rules in project context files.
Primary identity
Project context
What SOUL.md is
SOUL.md is primary identity: name, role, tone, hard limits. Official docs place it first in the system prompt. Prefer a short brief (~12–20 lines) over a one-line slogan.
Location: Hermes loads SOUL.md from the instance home only — typically ~/.hermes/SOUL.md or $HERMES_HOME/SOUL.md for a profile. It does not load SOUL from the project working directory. Personality stays stable across folders.
SOUL vs project context
If it should follow every session → SOUL.md. If it belongs to a repository or campaign → project context (AGENTS.md, .hermes.md / HERMES.md, or CLAUDE.md / .cursorrules when present). One project-context type loads per session (first match). SOUL still loads as identity.
- ·SOUL.md — identity, tone, limits (Hermes home only)
- ·AGENTS.md or .hermes.md — architecture, conventions, ports, project “never do X”
- ·/personality — temporary session overlay, not a SOUL replacement
- ·Context files are scanned for injection; review files from untrusted repos
Ready-to-adopt souls
Download a template, copy it to SOUL.md under this profile’s Hermes home, set the agent name, then start a new session.
Steps
A profile has SOUL.md under Hermes home (template or edited). The agent answers in that voice. You can state SOUL vs AGENTS.md in one sentence.
Stored on this device only — not sent anywhere.