Settings → Dream
During idle time, Mnemosyne OS bridges memories that resonate with each other. This page decides what those dreams are made of, and whether a model may read one on demand. The rail entry is Dream; the page subtitle reads During idle time, Mnemosyne OS bridges your memories by semantic resonance. Choose which categories feed those dreams — git and mechanical artifacts are never dreamed. Turning everything off pauses dreaming. Changes apply on the next idle scan.
For what the dreams are and where they surface, see Dream State. This page is about the settings.
Every switch on this page saves as soon as you touch it. There is no Save button and no restart: a change in the categories takes effect at the next idle scan. While the configuration loads the page says Loading…; if it cannot be read or written, the error is printed at the top, in English ("Failed to load dream config", "Failed to save dream config").
Which categories feed the dreams
Four rows, each a switch. Under each name, the app lists the raw spine ids the category covers, in English and without translation:
| Row | Spines covered | Default |
|---|---|---|
| Code | ARCHITECTURE · BUGFIX · SOURCE_CODE · DEPENDENCY | on |
| Ideas | EPIPHANY · IDEATIONAL · RESONANCE | on |
| Reflections | EMOTIONAL · SESSION · DIARY · THOUGHT · REFLECTION | on |
| Social | SOCIAL_POST · SOCIAL_NODE · REDDIT_COMMENT · REDDIT_POST | on |
The whole row is the click target. Git history and mechanical artifacts are not in any category: they are never dreamed, whatever you switch on.
Under the rows, a hint box: Dreams surface as low-weighted "leads to explore", never as authority. When all four rows are off, the box turns orange and reads Every category is off — dreaming is paused. That is the way to pause dreaming from this page.
Interpretation (LLM)
Optionally let an LLM read a dream's two endpoints on demand and flag a concrete finding. On-demand only, defaults to your local model, capped per day, and cached — most connections return nothing.
- Enable interpretation: off by default. Off, the dream viewer shows no "explore" button and no model call can happen. The controls below appear only once it is on.
- Model: two buttons, Local (free) (default) or Cloud.
- Look for: four chips you can combine: Bug, Security, Refactor, Insight. Bug, Security and Refactor are on by default; Insight is off. With all four off, an interpretation request is simply skipped.
- When to offer: which bridges get an "explore" button at all. Most surprising (default) offers it only on the bridges the engine considers orthogonal, the genuinely non-obvious ones; Balanced adds the bridges whose two ends are not near-duplicates; All offers it on every bridge. This filter is free: it decides what you can click, not what is computed.
- Max per day: a number from 0 to 500, default 20. Once the cap is reached, further explorations are skipped until the next day.
Under the cap, the hint reads Runs only when you click "explore" on a lead; re-exploring is free (cached). With the cap at 0, it turns orange: Cap is 0 — interpretation is paused.
Interpretation never runs on its own: it runs when you click "explore" on a lead, at most Max per day times a day, and a lead already explored is answered from the cache. With Cloud selected, each new exploration is a call to your cloud route, paid like any other; with Local (free) it stays on your machine.
The Dream State master switch, the dream layer reserve, auto-seal and the automatic dream schedule are not here. They are governed from the Dream dashboard, not from Settings → Dream.