Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Behavior bugAfter updating from beta to stable channel, two distinct bugs appeared: (1) agent replies are sent to the webchat interface instead of the originating Telegram thread, and (2) Telegram messages are automatically deleted by the agent/bot. [1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#84168•Fetched 2026-05-20 03:43:15
View on GitHub
Comments
1
Participants
2
Timeline
14
Reactions
1
Author
schenkei-codeschenkei-code
Participants
clawsweeper[bot]clawsweeper[bot]schenkei-codeschenkei-code
Timeline (top)
labeled ×9mentioned ×2subscribed ×2commented ×1

In beta channel 5, two distinct bugs appeared that did not exist in stable: (1) agent replies are sent to the webchat interface instead of the originating Telegram thread, and (2) Telegram messages are automatically deleted by the agent/bot. Stable channel worked correctly before switching to beta.

Root Cause

In beta channel 5, two distinct bugs appeared that did not exist in stable: (1) agent replies are sent to the webchat interface instead of the originating Telegram thread, and (2) Telegram messages are automatically deleted by the agent/bot. Stable channel worked correctly before switching to beta.

Code Example

NOT_ENOUGH_INFO — no server logs captured at time of incident. Agent confirmed behavior: "I replied in webchat instead of Telegram." User confirmed both missing replies and message deletions in Telegram thread.
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

In beta channel 5, two distinct bugs appeared that did not exist in stable: (1) agent replies are sent to the webchat interface instead of the originating Telegram thread, and (2) Telegram messages are automatically deleted by the agent/bot. Stable channel worked correctly before switching to beta.

Steps to reproduce

  1. Have agent running on stable channel (works correctly)
  2. Switch to beta channel 5
  3. Send a message to the agent via Telegram
  4. Two distinct issues occur: a) Agent processes the message but replies in the webchat interface instead of the Telegram thread b) Inbound and/or outbound Telegram messages are deleted automatically (bot message deletion behavior)

Expected behavior

  1. Agent replies should be sent back to the same Telegram thread where the inbound message originated, as was the case in stable channel.
  2. Messages should not be deleted automatically; they should persist in the Telegram chat history.

Actual behavior

  1. Agent replies should be sent back to the same Telegram thread where the inbound message originated, as was the case in stable channel.
  2. Messages should not be deleted automatically; they should persist in the Telegram chat history.

OpenClaw version

17.05.2026 beta channel 5 (stable channel was working correctly before)

Operating system

Linux (server-side), Telegram client on mobile/desktop

Install method

Docker VPS 1 Click hostinger

Model

kimi/k2p6 (agent model)

Provider / routing chain

Telegram provider → OpenClaw gateway

Additional provider/model setup details

Multi-channel setup with Telegram and webchat both configured. Issue appeared immediately after switching from stable to beta 5.

Logs, screenshots, and evidence

NOT_ENOUGH_INFO — no server logs captured at time of incident. Agent confirmed behavior: "I replied in webchat instead of Telegram." User confirmed both missing replies and message deletions in Telegram thread.

Impact and severity

• Affected users/systems/channels: Telegram users interacting with the agent • Severity: Blocks workflow — agent appears unresponsive to Telegram users; message deletion creates data loss / communication breakdown • Frequency: Consistent in beta 5 — both issues reproducible every time • Consequence: Missed Telegram messages, users must switch to webchat to see replies (breaks Telegram integration), plus loss of conversation history due to auto-deletion

Additional information

Regression in beta 5. Stable channel worked correctly — Telegram replies arrived in the Telegram thread and messages persisted. After switching to beta 5, both bugs appeared: (A) reply routing broken — replies go to webchat instead of Telegram thread, (B) message deletion — Telegram messages are auto-deleted by the bot/agent. Reverting to stable resolved both issues.

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

  1. Agent replies should be sent back to the same Telegram thread where the inbound message originated, as was the case in stable channel.
  2. Messages should not be deleted automatically; they should persist in the Telegram chat history.
#conversation history#indexing error#inference speed#output truncation#response parsing

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 [Bug]: Behavior bugAfter updating from beta to stable channel, two distinct bugs appeared: (1) agent replies are sent to the webchat interface instead of the originating Telegram thread, and (2) Telegram messages are automatically deleted by the agent/bot. [1 comments, 2 participants]