openclaw - 💡(How to fix) Fix Control UI: assistant messages don't render until page reload [1 comments, 1 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#70702Fetched 2026-04-24 05:54:26
View on GitHub
Comments
1
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
commented ×1

In the Control UI (web), assistant responses fail to appear in the chat after they're sent. Reloading the page reveals them.

Root Cause

In the Control UI (web), assistant responses fail to appear in the chat after they're sent. Reloading the page reveals them.

RAW_BUFFERClick to expand / collapse

Summary

In the Control UI (web), assistant responses fail to appear in the chat after they're sent. Reloading the page reveals them.

Environment

  • OpenClaw: 2026.4.22 (00bd2cf)
  • OS: macOS (Darwin 25.4.0)
  • Channel: Control UI (web)
  • Browser: Safari Version 26.4 (21624.1.16.11.4)

Repro

  1. Open Control UI
  2. Send a message to the assistant
  3. Assistant replies — but last message in reply does not render in the UI
  4. Reload the page to see the reply

extent analysis

TL;DR

The issue may be resolved by adjusting the rendering or update logic in the Control UI to properly display assistant responses without requiring a page reload.

Guidance

  • Verify if the issue is specific to Safari or if it occurs in other browsers to determine if it's browser-specific.
  • Check the network requests and responses to ensure the assistant's reply is being received by the client-side but not being rendered.
  • Investigate the rendering logic in the Control UI to see if there's an issue with updating the chat display after receiving new messages.
  • Consider adding logging or debugging statements to track when messages are received and when the UI is updated to help identify the issue.

Example

No specific code example can be provided without more details on the implementation, but checking the network requests and responses can be done using the browser's developer tools.

Notes

The issue might be related to how the Control UI handles updates or renders new messages. Without more information on the implementation, it's difficult to provide a precise fix.

Recommendation

Apply a workaround by implementing a periodic refresh of the chat log or adjusting the rendering logic to update in real-time, as upgrading to a fixed version is not mentioned as an option in the provided issue.

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