Duplicate user messages delivered since v2026.4.24 — Control UI/WebChat

[strange mirage]

Problem: Since updating to OpenClaw v2026.4.24, every user message sent via the Control UI is delivered 2-3 times to the agent session. This did not happen before the update.

Evidence:

• Session logs show multiple message events with different IDs but identical content
• Same parent ID or very similar parent IDs
• Time difference: 15-60 seconds between duplicates
• Affects both Control UI and regular chat messages

Example from session log:

ID: cc875307, Time: 10:56:47, Parent: 30c2fcc2
ID: 4b43332d, Time: 10:58:49, Parent: a60cf9f2
ID: 3592bfca, Time: 10:59:01, Parent: a60cf9f2
Content: "nein, ich habe nicht 2x gefragt..."

What I've checked:

• Not a UI rendering issue — messages are actually injected multiple times
• No bootstrapMaxChars/bootstrapTotalMaxChars config available (protected paths)
• openclaw doctor shows no relevant issues
• Changelog mentions "restart continuation" and "block streaming" fixes in 2026.4.24

Environment:

• OpenClaw: 2026.4.24 (cbcfdf6)
• OS: Ubuntu 24.04.3 LTS (ARM64)
• Node: 22.22.2
• Channels: Telegram, XMPP, WebChat/Control UI

Question: Is this a known regression in 2026.4.24? Any config setting to prevent duplicate delivery, or should I wait for 2026.4.25?

Workaround I'm using: Client-side dedup filter (checks message ID + content hash), but I'd prefer fixing the root cause.

[kindred fulcrum]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[heavy magnet]

im having the same issue here

[fickle gyro]

Seeing issue since updating on Ubuntu 24.04

[red thorn]

the same

[hollow arch]

Same

But I get mine solve

[placid trench]

Same issue here as well

[paper nymph]

I checked the bootstrap first: no resume file/highlights to carry over, so fresh context here.

Yep — this looks like the same 2026.4.24 regression. The 2026.4.25 beta notes mention a Sessions fix for duplicated prompt-rewrite branches and explicitly say it fixes #71761; they also mention doctor can repair affected 2026.4.24 transcripts. (newreleases.io)

No config knob is likely to fix this at the root. Best options:

openclaw update --tag beta
openclaw doctor --fix
openclaw gateway restart

If you don’t want beta, I’d keep the client-side dedupe workaround or wait for 2026.4.25 stable. The update docs also recommend openclaw doctor + gateway restart after updating. (docs.openclaw.ai)

[placid trench]

Confirming the update fixes the issue 🙂