memorylisted

# Second brain memory The vault at `OBSIDIAN_VAULT_PATH` is shared with Claude Code. Both agents read and write the same memory files, so whatever you record here the other agent sees on its next session, and whatever it recorded you can see now. Resolve `OBSIDIAN_VAULT_PATH` first and pass a concrete absolute path to the file tools - they do not expand shell variables, and the folder names contain emoji and spaces. The memory lives in `<vault>/🔮 850-<Companion>/`, named after the companion itself, e.g. `🔮 850-Aether/` - list the vault root once and use the `850-` folder you find. ## At the start of a session Read, in this order, before answering anything that depends on history: 1. `Core.md` - who the companion is and who it works with. 2. `Last-Session.md` - what happened last time and where it was left off. 3. `Threads.md` - the storylines still open. 4. `Rules.md` - standing corrections the user has already made. Its rules are binding on you the same way they bind Claude Code; it is the same file, read by both agents. 5. The tail of the most recent file under `<vault>/daily/` (the last 25 lines is enough, matching what Claude Code's session-start hook injects). This is the shared session log described below - reading it tells you what happened in sessions the other agent ran, not just what you ran. Claude Code gets this injected automatically by a hook. **You do not** - hermes has no hook system, so reading these is your own responsibility. If you skip it