openclaw - 💡(How to fix) Fix [Bug]: Agent repeats identical replies 2-10x on Telegram after 5.20 update

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…

After updating from 2026.5.12 to 2026.5.20, the agent sends duplicate identical replies on Telegram (2-10x per user message). Upgrading to 2026.5.22 reduced severity (~2-3x vs 8-10x) but did not fully fix.

Root Cause

After updating from 2026.5.12 to 2026.5.20, the agent sends duplicate identical replies on Telegram (2-10x per user message). Upgrading to 2026.5.22 reduced severity (~2-3x vs 8-10x) but did not fully fix.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After updating from 2026.5.12 to 2026.5.20, the agent sends duplicate identical replies on Telegram (2-10x per user message). Upgrading to 2026.5.22 reduced severity (~2-3x vs 8-10x) but did not fully fix.

Steps to reproduce

  1. Start Telegram conversation with agent on 2026.5.20+
  2. Send any user message
  3. Agent responds correctly — then sends same message again 2-10x

Expected behavior

Single reply per user message.

Actual behavior

Each user message triggers multiple identical agent replies. Severity increases over session lifetime (started 2x, grew to 8-10x on 5.20).

OpenClaw version

2026.5.22 (a374c3a)2026.5.22 (a374c3a)

Operating system

Linux Ubuntu 24.04, VirtualBox, x64

Install method

npm global

Model

deepseek/deepseek-v4-pro

Provider / routing chain

deepseek direct

Additional provider/model setup details

Lossless-claw v0.11.2 installed immediately before update. Session started on 5.20, carried through multiple restarts. The 5.22 fix "stop message-tool-only turns after successful source-channel message send" helped but didn't resolve. lossless-claw v0.11.2 was installed immediately before the 5.20 update

Logs, screenshots, and evidence

Impact and severity

Additional information

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

Single reply per user message.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING