Repository navigation
Description
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
After upgrading from 2026.4.23 to 2026.4.24, identical user messages are occasionally delivered twice to the session with the same timestamp but different seq numbers, causing the assistant to reply to both and producing duplicate visible messages in all channels (webchat and WeChat).
Steps to reproduce
- Run OpenClaw 2026.4.24 with webchat or WeChat channel configured
- Send a user message from the webchat UI or WeChat
- Observe session history via sessions_history API
- Same user message appears twice in transcript with identical timestamp but sequential seq numbers (e.g., seq 2703 and seq 2705)
- Assistant reply is also duplicated (seq 2704 and seq 2706) with same responseId
Expected behavior
In 2026.4.23, each user message was delivered exactly once. The same message should not appear twice in the session transcript.
Actual behavior
Same user message is delivered twice with identical timestamp but different __openclaw.id and sequential seq numbers. The assistant replies to both, producing duplicate visible messages. This happens intermittently, not on every message. Confirmed via sessions_history API showing duplicate entries for both user messages and assistant replies.
OpenClaw version
2026.4.24 (cbcfdf6)
Operating system
Linux 6.6.87.2-microsoft-standard-WSL2 (x64) / Windows 11 host
Install method
npm global
Model
bailian/qwen3.6-plus (also observed with nvidia-nim/z-ai/glm4.7)
Provider / routing chain
openclaw-weixin -> gateway -> bailian (dashscope) / webchat -> gateway -> bailian
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
Affected: All channels (webchat, WeChat)
Severity: Medium (annoying UX, duplicate visible messages, no data loss)
Frequency: Intermittent — not every message, but recurring across multiple sessions
Consequence: User sees duplicate messages in chat history, making conversations hard to follow
Additional information
Last known good version: 2026.4.23
First known bad version: 2026.4.24
Session history evidence from sessions_history API:
- User message seq 2703 at timestamp 1777207291784
- User message seq 2705 at same timestamp 1777207291784 (duplicate)
- Assistant reply seq 2704 at timestamp 1777207292059
- Assistant reply seq 2706 at same timestamp 1777207292059 (duplicate)
This pattern repeats multiple times (seq 2707-2710).
Possible related changes in 2026.4.24:
- Block streaming dedupe fix (Fixes Block-streaming channels deliver assembled final payload in addition to per-chunk streaming, causing full-reply duplication #70921)
- Gateway/sessions webchat mutation guard changes (Fixes fix(gateway): block webchat session compaction mutations #70716)
- Gateway/WebChat image attachment preservation (Fixes [Bug] User image attachments dropped when primary model lacks vision — imageModel fallback not honored #68513)
No workaround available — occurs at the session delivery layer.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
fix(chat): prevent duplicate user message delivery in 2026.4.24 regre…
fix(chat): prevent duplicate user message delivery in 2026.4.24 regre…
clawsweeper commentedon Apr 29, 2026
Thanks for the report. I checked current
main, but this shell is missing enough reproduction detail to verify a current bug.Close pending a current-version reproduction. The last human confirmation is from May, the relevant admission and transcript paths have changed substantially, and the previously active proposal closed without merging. The historical duplicate pairs do not establish which mechanism still fails.
Review details
Best possible solution:
Preserve identity-based deduplication in the existing admission and transcript owners, and repair only the boundary identified by a fresh correlated duplicate trace.
Do we have a high-confidence way to reproduce the issue?
No: the historical examples lack a deterministic trigger or current-version trace connecting one submission to duplicated processing and delivery; no runtime reproduction was executed.
Is this the best way to solve the issue?
Unclear: an idless-content fallback is not established as the appropriate repair because the report never demonstrates that missing message IDs caused these duplicates.
Security review:
Security review: This is a duplicate-delivery report without a demonstrated security boundary violation.
AGENTS.md: found and applied where relevant.
What I checked:
src/auto-reply/reply/inbound-dedupe.ts:80, 0cbbec027285)src/gateway/server-methods/chat-send-admission.ts:149, 0cbbec027285)src/auto-reply/reply/inbound-dedupe.test.ts:67, 0cbbec027285)src/auto-reply/reply/inbound-dedupe.ts, d87269045e4b)Likely related people:
Codex review notes: model internal, reasoning medium; reviewed against 6d299c3ab220.
fix(auto-reply): add content-hash fallback when MessageSid absent (op…
xilopaint commentedon May 3, 2026
This is still an issue in v2026.5.2.
schiles67 commentedon May 15, 2026
Can confirm this is still present in v2026.5.12.
From session analysis on May 14-15: 23% of all assistant text messages are duplicated in the session transcript — one entry with short 8-char ID, one with full UUID, identical content. These both get delivered to Telegram, causing every substantial response to appear twice.
Notable because it creates confusion when subagent results or status updates land as duplicate bubbles.
Happy to provide session traces if helpful for debugging.
25 remaining items
openclaw-barnacle commentedon Sep 19, 2026
This bug report has been automatically marked as stale due to inactivity.
ClawSweeper is checking whether current
mainalready fixes the reported behavior.Inactivity alone will not close a bug report.