openclaw - 💡(How to fix) Fix WebChat assistant replies still duplicate after #66875 fix (2026.4.27) [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#75239Fetched 2026-05-01 05:36:23
View on GitHub
Comments
1
Participants
2
Timeline
9
Reactions
2
Timeline (top)
mentioned ×4subscribed ×4commented ×1

Root Cause

Suspected root cause

Fix Action

Fix / Workaround

All merged in 4.27, but duplicates still occur.

The race condition between chat.final, session.message, and sessions.changed events can still trigger duplicate chat.history reloads that produce duplicate assistant bubbles, even with the #66875 mitigations in place.

RAW_BUFFERClick to expand / collapse

Bug type: Regression (worked before, now fails)

Issue #66875 fix is incomplete — WebChat ControlUI still duplicates every assistant reply on 2026.4.27.

Environment

  • OpenClaw: 2026.4.27 (cbc2ba0)
  • Channel: WebChat (ControlUI)
  • Install: npm global
  • OS: macOS (arm64)
  • Browser: Chrome

Steps to reproduce

  1. Open ControlUI WebChat
  2. Send any message
  3. Assistant reply appears as two identical message bubbles

Related fixes already in 4.27

IssueFix
#66875 / #66274skip redundant final-event history reloads
#72975 / #72963 / #72974coalesce duplicate in-flight submits
#72753bind WebChat handshakes to active socket

All merged in 4.27, but duplicates still occur.

Suspected root cause

The race condition between chat.final, session.message, and sessions.changed events can still trigger duplicate chat.history reloads that produce duplicate assistant bubbles, even with the #66875 mitigations in place.

extent analysis

TL;DR

The issue can be addressed by further refining the event handling to prevent race conditions between chat.final, session.message, and sessions.changed events.

Guidance

  • Review the event listeners for chat.final, session.message, and sessions.changed to ensure they are properly synchronized to avoid triggering duplicate chat.history reloads.
  • Verify that the fixes for issues #66875, #66274, #72975, #72963, #72974, and #72753 are correctly implemented and do not introduce new race conditions.
  • Consider adding additional logging or debugging statements to track the sequence of events and identify where the duplication occurs.
  • Evaluate the possibility of debouncing or throttling the event handlers to prevent multiple simultaneous triggers.

Example

No code example is provided due to the lack of specific implementation details in the issue.

Notes

The provided information suggests that the issue is related to a race condition, but without access to the codebase, it's challenging to provide a precise fix. The steps outlined are intended to guide the developer toward identifying and resolving the root cause.

Recommendation

Apply workaround: Refine event handling to prevent race conditions, as the issue persists despite previous fixes, indicating a need for further mitigation.

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

openclaw - 💡(How to fix) Fix WebChat assistant replies still duplicate after #66875 fix (2026.4.27) [1 comments, 2 participants]