Control Chat duplicate message isssue

[hasty sky]

Hi Krill — quick follow-up on the Control Chat duplicate-message issue.

I found a forum answer saying this looks like the same 2026.4.24 regression, and that 2026.4.25 beta mentions a Sessions fix for duplicated prompt-rewrite branches / issue #71761. Suggested fix there was:

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

What we already did locally:

• Updated to 2026.4.24
• Confirmed WhatsApp did not duplicate messages
• Control Chat duplicated both user and assistant bubbles
• Codex investigated and traced it to Control UI history merge keeping both local optimistic messages and persisted chat.history messages
• Applied a local UI-side dist workaround:
  • post-merge dedupe for nearby duplicate user/assistant messages
  • final runId guard
• Final Control Chat test works now
• Documented this in PATCH-NOTES.md

My current thinking:

• Since it works now, don’t rush into beta tonight
• Prefer waiting for 2026.4.25 stable
• Then run normal update + doctor --fix + gateway restart
• Let official fix overwrite/remove the local workaround if possible

Question: would you recommend moving to 2026.4.25 beta now to get the official fix, or stay on patched 2026.4.24 until stable? Also, when updating later, should I remove the local dist patch first, or just let the update overwrite it?

[odd karma]

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

[bronze egret]

I’d not jump to beta here. Two reasons:

1. 2026.4.25 stable is already published now, so the choice is really “patched 2026.4.24 vs stable 2026.4.25,” not beta vs wait. GitHub shows v2026.4.25 tagged Apr 27, and the changelog includes the Sessions fix for affected 2026.4.24 transcripts with duplicated prompt-rewrite branches / #71761. (github.com)
2. Since your local workaround is working, there’s no emergency — but I’d move to stable 2026.4.25 in your next maintenance window, not --tag beta.

Suggested later flow:

openclaw update --dry-run
openclaw update
openclaw doctor --fix
openclaw gateway restart
openclaw health

openclaw update is the recommended path and is documented as detecting install type, fetching latest, running doctor, and restarting; running doctor --fix + restart afterward is fine as a belt-and-suspenders check. (docs.openclaw.ai)