Keep Hermes project context and memory useful

01Keep project rules in AGENTS.md

The tips guide says Hermes loads the project-root AGENTS.md when a session starts. Put project conventions and architecture decisions there. It discovers subdirectory instruction files during relevant tool calls ^[1].

02Save facts and procedures separately

Use memory for durable facts, such as project locations or environment details. Use a skill for a repeatable procedure, per the Hermes guide ^[1]. Review remembered facts when the environment changes.

The memory documentation describes files that persist between sessions ^[2]. Avoid treating temporary task progress as a permanent preference.

03Inspect a long session before compressing it

Hermes documents these interactive commands ^[1]. Check usage first, then compress when the accumulated conversation needs shortening.

/usage

/compress

The guide describes compression as a summary of conversation history ^[1]. Keep important decisions in the project files too, so a later session does not depend on recovering every detail from that summary.

04Discover commands instead of guessing them

Type / and press Tab for the available commands and installed skills, as documented in the tips guide ^[1]. Use the choices shown by your installed version.