mem0-dream

Mem0 Dream — Memory Consolidation

This skill performs a memory consolidation pass: it fetches all project memories, identifies near-duplicates, flags contradictions, and prunes stale entries based on configured retention policies. All proposed changes are shown as a diff for user approval before anything is modified.

IMPORTANT: Execute steps strictly in order (1 → 2 → 3 → 4 → 5 → 6). Each step depends on the previous one. Do NOT run steps in parallel or skip ahead.

Step 1: Load Retention Policies

Check for a project config file in the project root (current working directory):

1. Look for .mem0.json first. If it exists, parse it as JSON and read the retention field (a dict of category → days | null).
2. If .mem0.json is not present, look for .mem0.md. If it exists, scan it for a retention: section or YAML front matter with retention settings and parse what you find.
3. If neither file exists, skip config loading entirely.

If no config is found or the config contains no retention settings, fall back to these built-in defaults:

metadata.type	Default retention
session_state	90 days
compact_summary	90 days
all others	no pruning

Store the resolved policies for use in Step 3.

---

Step 2: Fetch ALL Project Memories

Call get_memories to retrieve every memory for the active project:

get_memories(
    filters={"AND": [{"user_id": "<active_user_id>"}, {"app_id": "<active_project_id>"}]},
    page_size=200,
)

If the response indicates more pages exist, paginate until all memories are fetched. Collect the full list before proceeding. If zero memories are found, print:

No memories found for project <project_id>. Nothing to consolidate.

…and stop.

---

Step 3: Analyze — Find Issues

Work entirely in-memory; do not modify anything yet.

Group memories by metadata.type (use "unknown" when the field is absent). For each group, identify the following:

3a. Near-duplicate pairs (merge candidates)