openclaw - 💡(How to fix) Fix Control UI: Agent replies not displayed in chat window [1 participants]

Official PRs (…)
ON THIS PAGE

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#62386Fetched 2026-04-08 03:05:05
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

Fix Action

Workaround

  • Telegram channel works correctly - replies display fine
  • The issue appears specific to the Control UI / webchat interface
RAW_BUFFERClick to expand / collapse

Bug Description

Environment: OpenClaw Control UI (webchat), accessed via 127.0.0.1 OpenClaw Version: v2026.4.5 Browser: Safari on macOS

Issue: When user sends messages via Control UI (webchat), the agent responds (visible in logs) but the reply text is not displayed in the chat window.

Steps to Reproduce

  1. Open Control UI at http://127.0.0.1:18789/control/
  2. Select channel: telegram (or webchat)
  3. Send a message (e.g., "hello ?")
  4. Observe that the chat window shows:
    • User's message appears
    • Log shows "Piper 14:57 MiniMax-M2.7" indicating agent responded
    • But NO actual reply text from the agent is visible in the chat

Expected Behavior

  • Agent's reply text should appear in the chat window after the user's message

Actual Behavior

  • Log shows agent responded (timestamp + model shown)
  • But reply text is NOT displayed in the chat UI

Workaround

  • Telegram channel works correctly - replies display fine
  • The issue appears specific to the Control UI / webchat interface

Additional Notes

  • Session status shows agent is running and sending replies
  • The replies ARE being generated (visible in logs) but not rendered in UI
  • This creates confusion - users think agent is not responding

extent analysis

TL;DR

The issue can likely be mitigated by investigating the rendering of agent replies in the Control UI webchat interface, potentially involving a fix in the UI's handling of incoming messages.

Guidance

  • Verify that the issue is specific to the Control UI webchat interface by comparing its behavior with the Telegram channel, which is known to work correctly.
  • Investigate the UI's code responsible for rendering incoming messages to identify any potential bugs or inconsistencies that could prevent agent replies from being displayed.
  • Check the logs for any errors or warnings related to the rendering of agent replies in the Control UI webchat interface.
  • Consider comparing the message handling and rendering code between the Control UI webchat interface and the Telegram channel to identify any differences that could be contributing to the issue.

Notes

The provided information suggests that the issue is specific to the Control UI webchat interface and does not occur with the Telegram channel, indicating a potential problem with the UI's handling of incoming messages. However, without access to the code or more detailed logs, it is difficult to provide a more specific solution.

Recommendation

Apply workaround by using the Telegram channel for communication until the issue with the Control UI webchat interface can be resolved, as it is known to work correctly and can provide a temporary solution for users.

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