Keep a Hermes agent from rotting for six months
Tiny memory file, an Obsidian reference vault, scheduled skill pruning, a nightly dream loop and LLM-free daily backups.
Prompt for your agent
Goal: Run one long-lived agent without starting fresh every few weeks. Setup: agents used in source: Hermes Agent; tools/MCPs stated: Obsidian, cron, SQLite. Steps: 1. Keep the memory file at the default tiny size; first line: “Memory = only facts relevant to all conversations. Everything else → vault/skills.” 2. Keep an indexed reference/ folder in an Obsidian vault (one doc per system) as the shared source of truth; offload to it when memory hits ~75%. 3. Schedule skill pruning; deletions must declare what absorbed the content, pinned skills can be patched but not deleted. 4. Run a nightly dream job with a restricted toolset: review the day’s sessions, self-critique, write a dream log and insights file, audit skills, triage memory. 5. Back up daily/weekly/monthly with a no-agent cron script: WAL checkpoint before copying SQLite, verify integrity, include restore instructions. Rules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify. Based on: /u/ct06033 — https://www.reddit.com/r/hermesagent/comments/1x24qfp/my_hermes_configuration_that_works_for_me/
Steps are from the source. Includes a “Based on” credit line.
I tried this
Tell the next builder. One anonymous answer each; click again to undo.
Agents, models and tools only what the source states
- Agents
- Hermes Agent
- Tools
- Obsidian
- cron
- SQLite
Sources & credit
- /u/ct06033 primaryReddit · 10 Oct 2026https://www.reddit.com/r/hermesagent/comments/1x24qfp/my_hermes_configuration_that_works_for_me/