openclaw - 💡(How to fix) Fix [Bug]: DREAMS.md not created after successful REM phase; Control UI Dreams tab empty [1 comments, 2 participants]

name: Bug report description: Report defects, including regressions, crashes, and behavior bugs. title: "[Bug]: DREAMS.md not created after successful REM phase; Control UI Dreams tab empty" labels:

• bug body:

• type: markdown attributes: value: | Thanks for filing this report. Keep every answer concise, reproducible, and grounded in observed evidence. Do not speculate or infer beyond the evidence. If a narrative section cannot be answered from the available evidence, respond with exactly NOT_ENOUGH_INFO.

• type: dropdown id: bug_type attributes: label: Bug type options: - Behavior bug (incorrect output/state without crash) validations: required: true

• type: dropdown id: beta_blocker attributes: label: Beta release blocker options: - "No" validations: required: true

• type: textarea id: summary attributes: label: Summary placeholder: REM phase completes successfully and writes to memory/dreaming/rem/, but DREAMS.md is never created, leaving the Control UI Dreams tab empty. validations: required: true

• type: textarea id: repro attributes: label: Steps to reproduce placeholder: | 1. Enable memory-core dreaming in openclaw.json (dreaming.enabled: true, frequency: "30 23 * * *", timezone: "Asia/Shanghai") 2. Wait for scheduled dreaming run at 23:30 Shanghai time 3. Observe that memory/dreaming/rem/YYYY-MM-DD.md is created with REM phase output 4. Check workspace root — DREAMS.md does not exist 5. Open Control UI — Dreams tab shows no content validations: required: true

• type: textarea id: expected attributes: label: Expected behavior placeholder: | After a successful REM phase, DREAMS.md should be created/updated in the agent workspace root so the Control UI Dreams tab can display the Dream Diary content. Per docs: "Human-readable output in DREAMS.md" and "The Control UI exposes the same diary backfill/reset flow so you can inspect results in the Dreams scene." validations: required: true

• type: textarea id: actual attributes: label: Actual behavior placeholder: | memory/dreaming/rem/2026-04-26.md exists (2384 bytes) with REM phase content: "# REM Sleep\n\n### Reflections\n- No strong patterns surfaced.\n\n### Possible Lasting Truths\n..."

  DREAMS.md does NOT exist in workspace root.
  Control UI Dreams tab is completely empty — no diary entries shown.
  
  Evidence:
  - memory/dreaming/rem/2026-04-26.md: EXISTS with REM output (confirmed via file system)
  - DREAMS.md: DOES NOT EXIST (confirmed via file system and Control UI)
  - Control UI Dreams tab: Empty

  validations: required: true

• type: input id: version attributes: label: OpenClaw version placeholder: 2026.4.24 validations: required: true

• type: input id: os attributes: label: Operating system placeholder: Windows 11 validations: required: true

• type: input id: install_method attributes: label: Install method placeholder: npm global

• type: input id: model attributes: label: Model placeholder: minimax/MiniMax-M2.7-highspeed

• type: input id: provider_chain attributes: label: Provider / routing chain placeholder: openclaw gateway -> minimax API

• type: textarea id: logs attributes: label: Logs, screenshots, and evidence placeholder: | REM phase artifacts present: - memory/dreaming/rem/2026-04-26.md: 2384 bytes, content confirmed - phase-signals.json in memory/.dreams/: lightHits/remHits recorded

  DREAMS.md: absent from workspace root
  
  Config (dreaming section):
  {
    "enabled": true,
    "frequency": "30 23 * * *",
    "timezone": "Asia/Shanghai"
  }
  
  Related issues: PR #70523 (fixes #70509) addresses raw candidate pollution during fallback, but DREAMS.md creation failure is a separate issue.

  validations: required: true

• type: textarea id: impact attributes: label: Impact and severity placeholder: | Affected: Single-agent users with memory-core dreaming enabled Severity: Medium (Control UI feature gap — Dreams tab is non-functional) Frequency: Always — every dreaming run since feature was introduced in v2026.4.9 Consequence: Users cannot view the Dream Diary via Control UI; no workaround available to see dreaming output in the UI validations: required: true

• type: textarea id: additional_information attributes: label: Additional information placeholder: | Related: PR #68505 introduced two output modes (inline daily-note blocks vs separate reports). PR #70523 fixes raw candidate pollution in daily memory during fallback but notes "The fallback narrative still lands in DREAMS.md" — suggesting DREAMS.md SHOULD be written even on fallback. This issue may be a different code path where the fallback narrative also fails to write DREAMS.md.

  Environment: Windows 11, OpenClaw 2026.4.24, npm global install, memory-core plugin (built-in, not separate extension).

  validations: required: true