aio-dream

Dream: Memory Consolidation

You are performing a dream — a reflective pass over your memory files. Synthesize what you've learned recently into durable, well-organized memories so that future sessions can orient quickly.

Environment

• Memory directory: !echo "${CLAUDE_MEMORY_DIR:-$HOME/.claude/projects/$(pwd | sed 's|/|-|g')/memory}"
• Session transcripts: !echo "${CLAUDE_PROJECT_DIR:-$HOME/.claude/projects/$(pwd | sed 's|/|-|g')}" (JSONL files — each file is one past session)

Phase 1 — Orient

1. ls the memory directory to see what already exists
2. Read MEMORY.md to understand the current index
3. Skim existing topic files so you improve them rather than creating duplicates
4. If logs/ or sessions/ subdirectories exist (assistant-mode layout), review recent entries there

Phase 2 — Gather recent signal

Look for new information worth persisting. Sources in rough priority order:

1. Daily logs (logs/YYYY/MM/YYYY-MM-DD.md) if present — these are the append-only stream
2. Existing memories that drifted — facts that contradict something you see in the codebase now
3. Session transcripts — the transcript directory contains JSONL files of past sessions. Grep them for relevant context:

   grep -rn "<narrow term>" <transcript-dir>/ --include="*.jsonl" | tail -50
   

   Use narrow, specific terms relevant to what you found in Phase 1 (e.g., a project name, a tool, a decision topic). Read surrounding lines when a match looks valuable.

Phase 3 — Consolidate

For each thing worth remembering, write or update a memory file at the top level of the memory directory.

Memory file format

---
name: {{memory name}}
description: {{one-line description — used to decide relevance in future conversations, so be specific}}
type: {{user | feedback | project | reference}}
---

{{memory content}}

Memory types

Type	What to store	Scope
user	Role, goals, preferences, knowledge	Always private
feedback	User's guidance on approach — corrections AND confirmations	Private or team
project	Ongoing work, goals, bugs, incidents — NOT derivable from code/git	Bias toward team
reference	Pointers to external systems (Linear, Grafana, Slack, etc.)	Usually team