Lore
Documentation navigation
Docs/Use Lore/Run Dream safely

Run Dream safely

Run Dream manually, review output, and keep maintenance controlled.

Run Dream manually while you are still tuning Lore.

Dream reads memory and recall evidence, then proposes maintenance work. That can be useful, but it is still maintenance against durable memory. Treat each run like a small migration.

Safe process

  1. Back up memory first.
  2. Start a manual Dream run from the Web Console.
  3. Read the diary summary before looking at individual changes.
  4. Review proposed memory changes before accepting them.
  5. Check whether suggestions improve disclosure, glossary, priority, or content focus.
  6. Reject broad rewrites that mix unrelated topics.
  7. After accepting changes, run realistic recall queries to verify behavior.

When to avoid Dream

Do not run Dream as an automatic broad cleanup while:

  • embedding or View LLM settings are still unstable;
  • backups have not been verified;
  • many memories were just imported and have not been reviewed;
  • recall quality is poor because disclosure or glossary terms are missing.

Scheduled Dream runs are useful only after settings, backups, and review habits are stable.

Web ConsoleLearn what each main page in the Lore Web Console is used for.Recommended routineFollow a simple routine for memory review, recall checks, Dream, and backups.Write a durable memorySave one useful memory with path, priority, disclosure, glossary, and content.Use recall in chatRead the recall block as memory pointers and open useful memories before relying on them.