HermesYume

What HermesYume does

HermesYume is a Hermes port of Dreamer (clawdreamer), which did the same job for OpenClaw. A nightly job run by a systemd user timer reads settled sessions from state.db read-only, asks an LLM to extract typed claims, compares each with existing memories and stores long-term facts in LanceDB, in an NREM then REM sequence that ends in a Dream Log. In v2 the MEMORY.md and USER.md files stay the small always-on core, and the nightly job never writes to them.

A Hermes memory provider recalls only facts relevant to the current message, with at most five items or 1,000 characters per turn. Forgetting is a state: faded facts become dormant, no longer auto-recalled but still searchable and revived when they come up again. Strength is computed from importance and a half-life per kind of fact, not decremented. The tools yume_search, yume_remember and yume_forget are used only when the user asks, and inject: false runs a shadow mode for calibration.

Key features

• Nightly job that reads state.db read-only and extracts typed claims with an LLM
• LanceDB long-term store with provenance, history and computed strength
• Per-turn recall limited to five relevant facts
• Dormant state instead of deletion, with revival on reuse
• Shadow mode with inject: false for calibration
• Dated Dream Log for every run

When to use it

• Let Hermes keep long-term knowledge without filling MEMORY.md and USER.md
• Review what the agent learned each night through the Dream Log
• Calibrate recall behavior in shadow mode before turning injection on

Who it is for: Hermes Agent users whose MEMORY.md and USER.md are full and who want durable memory that grows and fades over time.

How it fits with Hermes Agent

It is a memory provider plugin for Hermes Agent that reads Hermes session data and leaves the built-in memory files untouched.

FAQ