concept · concepts/Dreaming (Offline Memory Consolidation).md

Dreaming (Offline Memory Consolidation)auto-ingested

status: active · created 2026-11-08 · 1 source · #agents #agent-memory #context-engineering #maintenance #auto-ingested

An agent uses idle time between tasks to reflect over its logs and transcripts. It corrects wrong notes, builds and prunes representations, promotes key notes into the always-loaded layer, and fills gaps a single session left behind. The model is sleep replay in the hippocampus, and the work builds on Letta/UC Berkeley's "sleep-time compute" (Anthropic — The Components of Agent Memory).

Explanation

In-session note-taking judges salience with partial information. Dreaming is the backward look that the forward-living session can't do. The source lists five jobs:

Job What it does Evidence
Correct Checks notes against the original transcript as ground truth Mt. Moon: a corrected location note got Claude to Cerulean City. The uncorrected run looped 3 times and never did.
Represent Builds and maintains an Agent-Maintained Wiki Stainless corpus: 13% → 48% over 2 → 128 sessions
Promote Moves key notes into the injected top layer, pushes detail down, leaves links Keeps the top layer (e.g. MEMORY.md) small
Focus Aims memory-building at a goal by tuning its instructions Contract wiki: 41/57 → 57/57 facts after a reflect-and-revise loop
Fill gaps Works across sessions to fix dangling links and add missing index pages 9 broken links repointed, 3 pages added

Costs and open questions. Dreaming needs compute, and checking every memory isn't practical. The source suggests aiming it at volatile information or setting its cadence by how often notes are accessed. Its output also isn't available until the pass ends.

Why it matters / where it shows up

  • This wiki's LINT is a dream pass. LINT covers contradictions, stale claims, orphans and missing pages, which matches "correct" and "fill gaps" almost exactly. INGEST's propagate step is "represent." The wiki runs LINT only when the human asks, so the source's cadence question applies here too. See Method Reflection (T5).
  • Terminology clash. Anthropic's "promote" means moving a note up the memory hierarchy into injected context. This wiki's PROMOTE means a seed graduating to grounded knowledge. These are different operations; don't conflate them.
  • The Human-in-the-Loop by Exception shape: expensive checking is done in a batch, offline, rather than inline on every action.

Open questions

  • What cadence should the wiki's own dream pass (LINT) run on? Fixed, or triggered by volume (e.g. every N auto-ingests)?
  • Dreaming checks notes against transcripts. This wiki's equivalent ground truth is raw/. Does LINT ever re-check pages against their raw sources, or only against each other?

Connections

  • Agent Memory — the system dreaming maintains.
  • Agent-Maintained Wiki — the representation dreaming builds.
  • Do It Once, at the Right Place — consolidation in a batch at a chosen time, instead of re-deciding in every session.
  • Method Reflection — LINT as dreaming, and the cadence question.
  • Navigation vs Search — the questions a dream pass asks (orphans, dangling links, what is load-bearing, what changed downstream) are navigation queries; the agent now has the graph CLI to run them by pointer.

Sources

The wiki is the source. This door reads it at build time and never writes to it.