openclaw - ✅(Solved) Fix [Bug]: Dream Diary tab markdown rendering broken [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62413Fetched 2026-04-08 03:04:38
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
commented ×1cross-referenced ×1referenced ×1

Fix Action

Fixed

PR fix notes

PR #62433: fix(ui): render markdown in Dream Diary tab

Description (problem / solution / changelog)

Summary

The Dream Diary tab in the Control UI displayed markdown source literally (e.g. **bold** rendered as literal **bold** instead of bold). Fix by applying the existing toSanitizedMarkdownHtml() pipeline to diary entry body text.

Root Cause

Diary entries were rendered as plain text by splitting on newlines and wrapping each line in a <p> tag. The markdown was never parsed — it was displayed verbatim.

Fix

  • ui/src/ui/views/dreaming.ts: Replace plain-text paragraph rendering with ${unsafeHTML(toSanitizedMarkdownHtml(entry.body))}
  • ui/src/styles/dreams.css: Add .dreams-diary__prose CSS for rendered markdown elements (p, strong, em, code), preserving the original italic style

Testing

Verified by inspection of:

  • ui/src/ui/chat/grouped-render.ts which already uses toSanitizedMarkdownHtml for chat messages
  • The diary entry body flow: parseDiaryEntries -> entry.body -> rendered as plain text

Fixes

Fixes: #62413

Changed files

  • ui/src/styles/dreams.css (modified, +29/-1)
  • ui/src/ui/views/dreaming.ts (modified, +3/-8)
RAW_BUFFERClick to expand / collapse

Bug Description

The Dream Diary tab in the Control UI has broken markdown rendering. Markdown formatting is displayed literally instead of being rendered properly.

Screenshot

<img width="1600" height="902" alt="Image" src="https://github.com/user-attachments/assets/9332d102-e3b7-42ee-b8b4-168df30846ce" />

Current Behavior

  • renders as literal instead of Bold text
  • Markdown asterisks are visible in the UI
  • Inconsistent styling between different sections

Expected Behavior

  • Markdown should be properly rendered (bold, italics, headers, etc.)
  • Text formatting should be consistent throughout the diary view

Environment

  • OpenClaw version: v2026.4.5
  • Control UI > Dreaming > Dream Diary tab

Steps to Reproduce

  1. Enable dreaming in config
  2. Write a dream entry with markdown formatting (e.g., , )
  3. Open Control UI > Dreaming > Dream Diary
  4. Observe that markdown syntax is displayed literally

Additional Context

The dream file is stored at with standard markdown formatting. The UI appears to be escaping or not processing the markdown correctly.

extent analysis

TL;DR

The issue is likely due to improper markdown rendering in the Control UI, and a workaround may involve adjusting the UI's markdown processing or escaping.

Guidance

  • Verify that the markdown formatting in the dream file is correct and consistent with the expected syntax.
  • Check the Control UI's configuration or code for any markdown rendering or escaping settings that may be causing the issue.
  • Test the markdown rendering in other sections of the Control UI to see if the issue is specific to the Dream Diary tab.
  • Consider using a markdown rendering library or function to process the dream file content before displaying it in the UI.

Example

No code snippet is provided as the issue does not contain sufficient information about the UI's code or configuration.

Notes

The issue may be specific to the OpenClaw version (v2026.4.5) or the Control UI's implementation, and further investigation is needed to determine the root cause.

Recommendation

Apply a workaround, such as using a markdown rendering library or adjusting the UI's markdown processing settings, as the issue is likely related to the UI's rendering of markdown content.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING