Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix WebChat: new message replaced by previous message content — delivery-mirror replay race

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…

Error Message

WebChat messages are silently lost. The user sends a message, nothing happens (no response, no error), and the message disappears from the chat history as if it was never sent. The user must retype and resend the message — sometimes multiple times — before it gets through.

  • If message delivery fails, an error should be shown, not silent loss
  • Session JSONL shows 6 instances of "synthetic error / missing tool result" annotations, suggesting some infra-level delivery failure
RAW_BUFFERClick to expand / collapse

Describe the bug

WebChat messages are silently lost. The user sends a message, nothing happens (no response, no error), and the message disappears from the chat history as if it was never sent. The user must retype and resend the message — sometimes multiple times — before it gets through.

This bug is actively occurring and directly degrading the user experience.

Steps to reproduce

  1. Use WebChat (direct webchat, not via Control UI proxy)
  2. Send a message during an active conversation
  3. Observe: sometimes the message simply disappears — no assistant response, message gone from rendered history

Hard to reliably reproduce, but observed frequently in long-running sessions.

Expected behavior

  • Sent messages should always appear in history
  • If message delivery fails, an error should be shown, not silent loss
  • Messages should never disappear from history

Environment

  • OpenClaw version: 2026.5.7 (eeef486)
  • Channel: webchat (direct)
  • Model: zai/glm-5.1
  • Deployment: self-hosted on CentOS Stream 9, x86_64, Node v22.22.0
  • Compaction: enabled (reserveTokens=40000, keepRecentTokens=30000)

Additional context

  • This appears related to the broader delivery-mirror / duplicate-message family tracked in #69208
  • #40716 (delivery-mirror filter, canonical for #69208 Track B) was closed unmerged, though partial dedupe fixes landed via #67185 and #45489
  • Similar symptoms reported in #53408 (tool params silently dropped after long conversations) and #67999 (Control UI doesn't render new messages dynamically)
  • In this session, the "Tavily API" question appeared 3 times in the session JSONL (lines 4042, 4056, 4059) — each treated as a new message but likely the same message resent due to loss
  • Session JSONL shows 6 instances of "synthetic error / missing tool result" annotations, suggesting some infra-level delivery failure
  • No errors in journalctl output matching the timeframe

Impact

High — users lose messages, waste time retyping, and cannot trust that sent messages are actually delivered. Combined with the "replying to previous message" bug (#69208), this makes sustained WebChat use unreliable.

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…

FAQ

Expected behavior

  • Sent messages should always appear in history
  • If message delivery fails, an error should be shown, not silent loss
  • Messages should never disappear from history
#api#inference speed#output truncation#response parsing#generation 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 WebChat: new message replaced by previous message content — delivery-mirror replay race