Dreaming on but no Memory palace population. | Friends of the Crustacean 🦞🤝 | Page 1

dusky leaf Apr 16, 2026, 2:01 PM

#

Memory palace is not populated

spark shuttleBOT Apr 16, 2026, 2:03 PM

#

If by “memory palace” you mean long-term memory / MEMORY.md, a few gotchas:

dreaming is off by default
even when enabled, it runs on a schedule by default, not instantly
only the deep phase writes to MEMORY.md
deep promotion is thresholded, so weak/low-repeat items won’t populate it

Also, the docs call this Dreaming / MEMORY.md, not “memory palace”, so I want to make sure we’re looking at the same thing.

Can you paste these?

openclaw --version
openclaw status
openclaw memory status --deep
openclaw memory promote

#

And from chat:

/dreaming status

If openclaw memory promote shows candidates, try:

openclaw memory promote --apply

If it shows nothing, the usual causes are:

dreaming not enabled (plugins.entries.memory-core.config.dreaming.enabled: true)
not enough short-term material yet
the scheduled sweep hasn’t run yet

#

One more important nuance: Dreams/backfill does not directly fill MEMORY.md. Historical replay goes into DREAMS.md / short-term staging first, then deep promotion decides what becomes durable.

Docs:

Paste the outputs and I’ll help narrow it down.

dusky leaf Apr 16, 2026, 5:57 PM

#

In the OpenClaw interface we have the Dreaming page, here we have the scene tab, diary tab and the advanced tab. undert he diary tab we have Dreams, imported insights and Memroy palace ( Memory palace is not populated yet
Right now the wiki mostly has raw source imports and operational reports. This tab becomes useful once syntheses, entities, or concepts start getting written.)

spark shuttleBOT Apr 16, 2026, 5:59 PM

#

Ah, got it, thanks, that helps.

That empty Memory Palace tab does not usually mean dreaming is broken. It means the wiki layer does not have higher-level pages yet.

In practice:

Dreams = dream diary / dreaming output
Imported Insights = imported/raw source material
Memory Palace = compiled memory-wiki pages, mainly:
- syntheses
- entities
- concepts

Raw source imports and operational reports do not populate that tab by themselves. That empty-state text is basically saying exactly that.

So if you only have imported chats / reports so far, empty Memory Palace is expected.

#

Quick checks:

openclaw --version
openclaw wiki status

If wiki status shows something like:

sources > 0
reports > 0
entities = 0
concepts = 0
syntheses = 0

then the UI is behaving normally.

Important nuance:

#

openclaw wiki compile refreshes existing wiki pages
it does not invent syntheses/entities/concepts out of thin air

So to actually populate Memory Palace, something needs to write wiki pages in those categories, for example via a wiki authoring flow (wiki_apply, ingest workflows, etc.) with memory-wiki enabled.

Docs:

If you paste the output of openclaw wiki status, I can tell you in one glance whether this is just “expected empty” or an actual bug.

dusky leaf Apr 16, 2026, 6:02 PM

#

openclaw memory status --deep:

◓ Probing embeddings…[node-llama-cpp] The prebuilt binary for platform "linux" "x64" with Vulkan support is not compatible with the current system, falling back to using no GPU
◇
Memory Search (sarah)
Provider: local (requested: local)
Model: /home/najef/.cache/qmd/models/hf_ggml-org_embeddinggemma-300M-Q8_0.gguf
Sources: memory
Indexed: 10/12 files · 98 chunks
Dirty: no
Store: ~/.openclaw/memory/sarah.sqlite
Workspace: ~/.openclaw/agents/sarah
Dreaming: 0 3 * * * · limit=10 · minScore=0.8 · minRecallCount=3 · minUniqueQueries=3 · recencyHalfLifeDays=14 · maxAgeDays=30
Embeddings: ready
By source:
memory · 10/12 files · 98 chunks
Vector: ready
Vector dims: 768
Vector path: ~/.nvm/versions/node/v24.14.1/lib/node_modules/openclaw/node_modules/sqlite-vec-linux-x64/vec0.so
FTS: ready
Embedding cache: enabled (115 entries)
Batch: disabled (failures 0/2)
Recall store: 73 entries · 0 promoted · 73 concept-tagged · 41 spaced · scripts=73 latin
Recall path: ~/.openclaw/agents/sarah/memory/.dreams/short-term-recall.json
Recall updated: 2026-04-14T01:05:52.924Z
Dreaming artifacts: diary present · 1 corpus files · ingestion state present
Dream corpus: ~/.openclaw/agents/sarah/memory/.dreams/session-corpus
Dream ingestion: ~/.openclaw/agents/sarah/memory/.dreams/session-ingestion.json
Dream diary: ~/.openclaw/agents/sarah/DREAMS.md
najef@OpenClaw-Server:~$ openclaw memory promote

spark shuttleBOT Apr 16, 2026, 6:03 PM

#

This is helpful.

A few reads from that output:

the Vulkan fallback warning is harmless here
embeddings are ready
the recall store is populated (73 entries)
dreaming artifacts exist (DREAMS.md, corpus, ingestion state)
but nothing has been promoted yet (0 promoted)

So memory-core is clearly collecting material. What it does not show is anything about the wiki layer, which is what drives the Memory Palace tab.

So right now the most likely state is:

dreaming is working
deep promotion has not promoted anything into durable memory yet
memory-wiki still has no entities / concepts / syntheses, so Memory Palace stays empty

#

One thing I do notice: Recall updated is 2026-04-14, which is a bit stale if the sweep is meant to run daily. So I’d check both the promotion path and the wiki path next.

Can you paste these 3?

openclaw --version
openclaw memory promote
openclaw wiki status

What I expect:

if memory promote shows no candidates, then nothing is clearing the current deep thresholds yet
if wiki status shows 0 entities, 0 concepts, 0 syntheses, then the empty Memory Palace is expected, not a UI bug

Docs:

https://docs.openclaw.ai/concepts/dreaming

#

https://docs.openclaw.ai/plugins/memory-wiki

Paste those and I can narrow it down pretty fast.

dusky leaf Apr 16, 2026, 6:03 PM

#

najef@OpenClaw-Server:~$ openclaw --version
openclaw wiki status
OpenClaw 2026.4.14 (323493f)

🦞 OpenClaw 2026.4.14 (323493f) — Open source means you can see exactly how I judge your config.

Wiki vault mode: isolated
Vault: ready (/home/najef/.openclaw/wiki/main)
Render mode: native
Obsidian CLI: missing
Bridge: enabled
Unsafe local: disabled
Pages: 0 sources, 0 entities, 0 concepts, 0 syntheses, 6 reports
Source provenance: 0 native, 0 bridge, 0 bridge-events, 0 unsafe-local, 0 other
najef@OpenClaw-Server:~$

spark shuttleBOT Apr 16, 2026, 6:04 PM

#

Yep, this explains it.

Your setup is not broken, it’s just currently set up in a way that leaves Memory Palace empty:

version is fine: 2026.4.14
wiki status shows 0 entities, 0 concepts, 0 syntheses
it only has 6 reports
and your wiki is in vaultMode: isolated

That combination means the Dreaming UI has basically nothing “palace-worthy” to show yet.

Why:

Memory Palace is for higher-level memory-wiki pages, mainly:
- entities
- concepts
- syntheses

#

reports alone generally won’t populate it
isolated mode means the wiki is not really acting as a bridge from your active memory layer

So the short version is:

dreaming can be on, recall can be populated, and the wiki can still show an empty Memory Palace if no entity/concept/synthesis pages exist.

If you want the wiki to pull from your memory layer, switch memory-wiki to bridge mode instead of isolated mode.

Docs-backed config shape:

plugins: {
  entries: {
    "memory-wiki": {
      enabled: true,
      config: {

#

        vaultMode: "bridge",
        bridge: {
          enabled: true,
          readMemoryArtifacts: true,
          indexDreamReports: true,
          indexDailyNotes: true,
          indexMemoryRoot: true,
          followMemoryEvents: true,
        },
      },
    },
  },
}

Two important notes:

#Dreaming on but no Memory palace population.