Context Files
Context Files
Start with meaning, then move to detail.
This lesson explains Context Files 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 Supported Context Files, AGENTS.md, Directory Chain (git root → working directory), then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand Context Files 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.
Project context files — .hermes.md, AGENTS.md, CLAUDE.md, global SOUL.md, and .cursorrules — automatically injected into every conversation
What does the source say, and in what order?
- 01Supported Context Files
Start here to understand the core idea or structure.
- 02AGENTS.md
Read this after the foundation, then connect it to the previous step.
- 03Directory Chain (git root → working directory)
Read this after the foundation, then connect it to the previous step.
- 04Progressive Subdirectory Discovery
Read this after the foundation, then connect it to the previous step.
- 05Example AGENTS.md
Read this after the foundation, then connect it to the previous step.
- 06Architecture
Read this after the foundation, then connect it to the previous step.
- 07Conventions
Read this after the foundation, then connect it to the previous step.
- 08Important Notes
Read this after the foundation, then connect it to the previous step.
- 09SOUL.md
Read this after the foundation, then connect it to the previous step.
- 10.cursorrules
Finish here to verify the result and special cases.
Copy only after you understand the effect.
monorepo/ (git root, cwd = packages/webapp/)
├── AGENTS.md ← Loaded first (repo-wide conventions)
└── packages/
├── AGENTS.md ← Loaded second
└── webapp/
└── AGENTS.md ← Loaded last (most specific, takes precedence)my-project/
├── AGENTS.md ← Loaded at startup (system prompt)
├── frontend/
│ └── AGENTS.md ← Discovered when agent reads frontend/ files
├── backend/
│ └── AGENTS.md ← Discovered when agent reads backend/ files
└── shared/
└── AGENTS.md ← Discovered when agent reads shared/ files## SOUL.md
`SOUL.md` controls the agent's personality, tone, and communication style. See the [Personality](/user-guide/features/personality) page for full details.
**Location:**
- `~/.hermes/SOUL.md`
- or `$HERMES_HOME/SOUL.md` if you run Hermes with a custom home directory
Important details:
- Hermes seeds a default `SOUL.md` automatically if one does not exist yet
- Hermes loads `SOUL.md` only from `HERMES_HOME`
- Hermes does not probe the working directory for `SOUL.md`
- If the file is empty, nothing from `SOUL.md` is added to the prompt
- If the file has content, the content is injeRead 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.