Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] TUI duplicate message rendering after websocket reconnect — regression in 2026.4.24 [2 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#71838•Fetched 2026-04-26 05:07:39
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
0
Author
leetaurleetaur
Participants
leetaurleetaursteipetesteipete
Timeline (top)
commented ×2closed ×1cross-referenced ×1

Messages render twice (duplicated) in TUI after websocket reconnect. This started immediately after updating to 2026.4.24.

Root Cause

Messages render twice (duplicated) in TUI after websocket reconnect. This started immediately after updating to 2026.4.24.

Fix Action

Workaround

Downgrade to 2026.4.23:

npm uninstall -g openclaw
npm install -g [email protected]

Or restart gateway before each TUI session:

openclaw gateway restart

Code Example

npm uninstall -g openclaw
npm install -g openclaw@2026.4.23

---

openclaw gateway restart
RAW_BUFFERClick to expand / collapse

Description

Messages render twice (duplicated) in TUI after websocket reconnect. This started immediately after updating to 2026.4.24.

Reproduction

  1. Run openclaw gateway restart (clears duplication temporarily)
  2. Open TUI with openclaw tui — messages render cleanly
  3. Close TUI / disconnect
  4. Reopen TUI — all messages now render twice
  5. Same behavior in browser (Chromium/Firefox) Control UI

Environment

  • OpenClaw version: 2026.4.24 (cbcfdf6)
  • OS: Linux 6.1.0-44-amd64 (x64)
  • Node: v25.9.0 (nvm)
  • Gateway: systemd service, port 18789, loopback only

Behavior

  • Duplication triggers on websocket reconnect
  • Gateway restart temporarily fixes it
  • Affects both TUI and browser Control UI
  • Agent itself is fine (single message in transcript) — rendering layer bug
  • Browser can crash from duplication loops

Workaround

Downgrade to 2026.4.23:

npm uninstall -g openclaw
npm install -g [email protected]

Or restart gateway before each TUI session:

openclaw gateway restart

Related

This matches closed issue #34331 (fixed in #34375), but that fix appears to have regressed in 2026.4.24. Issue was closed April 20, 2026 — updated to 2026.4.24 on April 25 and immediately hit the bug.

Impact

  • TUI becomes unusable after reconnect without gateway restart
  • Browser Control UI can crash from rendering loops
  • Forces users to stay on 2026.4.23 or keep restarting gateway

extent analysis

TL;DR

Downgrade to OpenClaw version 2026.4.23 to prevent message duplication in TUI after websocket reconnect.

Guidance

  • The issue is likely caused by a regression in the rendering layer, introduced in version 2026.4.24, which was previously fixed in #34375.
  • To verify the issue, follow the reproduction steps provided, which involve restarting the gateway, opening TUI, closing and reopening it to observe the message duplication.
  • As a temporary workaround, restarting the gateway before each TUI session using openclaw gateway restart can prevent the duplication.
  • Downgrading to version 2026.4.23 using npm install -g [email protected] is a more permanent solution until the regression is fixed.

Example

No code snippet is necessary for this issue, as the provided workarounds are command-line based.

Notes

The provided workarounds may not be ideal for long-term use, as they either require frequent manual intervention or revert to an older version. It is recommended to monitor for updates to OpenClaw that address this regression.

Recommendation

Apply the workaround by downgrading to version 2026.4.23, as it is a more reliable solution than constantly restarting the gateway, and wait for a future update that fixes the regression.

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…
#callback error#memory management#API rate limit#retriever error#indexing error

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 [Bug] TUI duplicate message rendering after websocket reconnect — regression in 2026.4.24 [2 comments, 2 participants]