dream

Files (1)

• SKILL.md

SKILL.md (first lines)

# Dream

A consolidation pass. It mutates memory, so the default is propose-then-confirm; `--auto` applies only the safe merges without asking.

Read the curated set with `get_memories` using `exclude_sources: ["session", "archived"]` and `limit` 1000 — raw captures are never consolidation targets (distillation owns their lifecycle).

**Completeness gate — check before anything else.** Compare the returned count against the response's `total_matching`. If fewer memories came back than matched — or the response has no `total_matching` field at all (server predates the filter patch) — you are looking at a partial, arbitrarily-sampled view. **Propose nothing destructive from a partial view**: a "duplicate" whose twin is outside the window isn't a duplicate, and a "contradiction" may already be resolved by an unseen entry. Report the truncation, suggest raising the limit, and stop.

With the full set in hand, work out a plan in three buckets:

**Merge** — groups of near-duplicates. Pick the clearest wording (or compose one that covers the group), and plan to replace the group with it.

**Resolve** — contradictory pairs. The newer `created_at` usually wins, but if it's ambiguous, ask rather than guess.

**Prune** — only entries that are clearly dead: superseded by a merge, or pointing at a tool/path the repo no longer has. When unsure, keep it.

Show the plan as a diff before touching anything:

```
## dream — 412 of 412 curated memories scanned
merge 3 → 1: "deploys via CI" (drops [mem0:a1],[mem0:b2],[mem0:c3])
resolve: keep [mem0:d4] (2026-06), drop [mem0:e5] (2026-01)
prune: [mem0:f6] — references the old Traefik route
```

On approval, apply each: a merge is `add_memory` of the kept text (`infer=false`, carry the type) followed by `delete_memory` on the originals; a resolve/prune is `delete_memory`. There's no rollback, so finish only after the writes succeed and report the net change.

`--auto` runs merges of obvious duplicates silently and leaves contradictions and prunes for a human. The completeness gate applies to `--auto` too — a truncated fetch means no automatic changes at all.

From pjope/mem0-selfhosted-hooks, MIT.

More from pjope/mem0-selfhosted-hooks