hermes-dreaming

Русская версия

Nightly, deterministic memory consolidation ("dreaming") for Hermes Agent, in the spirit of OpenClaw dreaming.

An agent's memory goes wrong in two quiet ways: useful facts never make it into durable memory, and durable memory fills up with stale or duplicated entries until the char limit silently stops all writes. Every night a Python script looks at what the agent knows and what people actually said, and wakes the agent only when there is something to decide. The rules call no LLM and the script never writes memory; the agent applies its proposals through the regular memory tool and reports in a few lines. An optional cloud judge, off by default, can second-guess the rules' mention count — see below.

Task outcomes and recorded explanations (3.6.0)

With holographic 0.20.0 or later, read how stored facts helped or failed a task, separately from their truth/trust:

python3 skills/dreaming/scripts/dream.py --memory-outcomes
python3 skills/dreaming/scripts/dream.py --memory-explain ATTEMPT_ID --memory-format text

Enable collection in the provider (experience: on; optional experience_trace: on). Add "task_outcomes": true to dreaming.json to include count-only summaries in the normal nightly report. Default is off. No additional model wakeup or network call is added, no correction text is copied into a lesson cache, and nothing automatically changes trust, ranking or MEMORY.md. Revisions count as one active outcome per attempt; these remain agent reports.

The default is the configured profile store. A scoped store requires an explicit --memory-store already allowed by chat_stores.promote_from; reports never join stores, and since 3.7.0 the JSON summary names its store ("store"). Old providers report unsupported and continue normal dreaming. See docs/experience.md for retention, erase boundaries, JSON output and limitations.

How it works

This is the beginning of the README. Read the rest at the original. Read the full README ↗