openclaw - 💡(How to fix) Fix [Bug] Telegram DM sends silent reply messages like 'No further word from me' after update to 2026.4.23 [1 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#71657Fetched 2026-04-26 05:10:12
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
2
Author
Participants
RAW_BUFFERClick to expand / collapse

Bug Description

Telegram direct-message turns that end with no visible final reply emit synthetic user-facing bubbles like 'No further word from me' or 'Nothing new to add from my side' instead of staying silent.

This started after updating to OpenClaw 2026.4.23 (from 2026.4.14).

Environment

  • OpenClaw version: 2026.4.23
  • Channel: Telegram (direct DM)
  • Model: minimax/MiniMax-M2.7
  • OS: macOS

Steps to Reproduce

  1. Have a Telegram DM conversation with the bot
  2. Bot processes a request that results in no visible final reply (or after compaction)
  3. User sees 'No further word from me.' or 'Nothing new to add from my side.' message

Expected Behavior

The bot should stay silent when there's no actual response to send, not send synthetic messages.

Related Issues

This appears to be related to issue #70628 which describes the same behavior with slightly different message text.

extent analysis

TL;DR

Downgrade to OpenClaw version 2026.4.14 to potentially resolve the issue of synthetic user-facing bubbles being emitted when there's no visible final reply.

Guidance

  • Verify that the issue is indeed caused by the update to OpenClaw 2026.4.23 by checking if the problem persists when downgrading to the previous version.
  • Review the release notes for OpenClaw 2026.4.23 to see if there are any known issues or changes related to Telegram direct-message handling.
  • Check if issue #70628 provides any additional insights or workarounds that could be applied to this problem.
  • Test the bot's behavior with different models or channels to determine if the issue is specific to the minimax/MiniMax-M2.7 model or Telegram direct messages.

Example

No code snippet is provided as the issue does not imply a specific code-related fix.

Notes

The solution is based on the information provided and may not be applicable if other factors are contributing to the issue. Further investigation into the changes made in OpenClaw 2026.4.23 may be necessary to determine the root cause.

Recommendation

Apply workaround: Downgrade to OpenClaw version 2026.4.14, as it is the last known working version before the issue started occurring.

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…

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] Telegram DM sends silent reply messages like 'No further word from me' after update to 2026.4.23 [1 participants]