When to use Dream
Use Dream after a burst of recording, before a planning round, or when query results feel noisy. Do not run Dream on every task. The proposals are more useful when there is enough saved memory to compare.Dream works on the space resolved from the current project folder. If the project should use a named space, bind it first with Bind.
Ask the agent to review memory
Ask your agent:Choose a mode
Dream supports four modes.| Mode | What it proposes |
|---|---|
merge | Topics that cover the same ground and may be combined. |
link | Topics that should reference each other but do not yet link. |
prune | Topics that look stale or low-value. |
synthesize | Small related topics that may read better as one larger topic. |
merge.
Manual examples:
Review the candidates
Dream returns JSON with candidate paths, scores, and the reason the topics were grouped. Ask the agent to read source topics before acting:Act on a proposal
Only act on candidates that still make sense after reading the source topics.| Dream proposal | Follow-up action |
|---|---|
merge | Use merge.mjs to fold one topic into another and remove the loser. |
link | Use Record to update related= references. |
prune | Use prune.mjs to remove stale topics after confirming they are safe to delete. |
synthesize | Use synthesize.mjs to write a consolidated topic and absorb the smaller topics. |