openclaw - 💡(How to fix) Fix WebChat UI: agent responses rendered as duplicate messages [2 comments, 3 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#72641Fetched 2026-04-28 06:33:43
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
1
Timeline (top)
commented ×2closed ×1cross-referenced ×1mentioned ×1
RAW_BUFFERClick to expand / collapse

Bug Description

In the OpenClaw WebChat control UI (openclaw-control-ui), agent responses are sometimes rendered as two identical chat bubbles. Both duplicates carry the same metadata (token counts, context usage percentage), confirming this is a client-side rendering bug — the server only sends the message once.

Steps to Reproduce

  1. Use OpenClaw WebChat UI (webchat surface)
  2. Send a message to the agent and wait for a reply
  3. Observe the reply appearing twice with identical reply stats

Expected Behavior

Each agent reply should render exactly once.

Screenshot

(Screenshot available showing two identical messages with same ↑↓ R ctx stats)

Environment

  • OpenClaw version: 2026.4.24 (cbcfdf6)
  • Channel: webchat (openclaw-control-ui)

Reported via Xiake agent

extent analysis

TL;DR

The client-side rendering bug in the OpenClaw WebChat control UI can likely be fixed by modifying the rendering logic to prevent duplicate messages.

Guidance

  • Review the rendering logic in the openclaw-control-ui to identify why duplicate messages are being rendered.
  • Verify that the server is indeed sending each message only once by inspecting the network requests and responses.
  • Check for any caching or buffering issues that might be causing the duplicate rendering.
  • Consider adding a unique identifier to each message and checking for its presence before rendering to prevent duplicates.

Example

No code snippet can be provided without more information about the rendering logic, but a possible approach could involve checking for existing messages before rendering a new one.

Notes

The fix may require modifications to the openclaw-control-ui code, and the exact solution will depend on the specifics of the rendering logic.

Recommendation

Apply a workaround by modifying the rendering logic to prevent duplicate messages, as the root cause appears to be a client-side 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