Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: Bug Report: Silent Reply "All quiet on my side." Message Appearing Repeatedly - $10 Wasted Debugging [2 pull requests, 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#78188•Fetched 2026-05-06 06:16:09
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
2
Author
yurivongxay-rgbyurivongxay-rgb
Participants
clawsweeper[bot]clawsweeper[bot]yurivongxay-rgbyurivongxay-rgb
Timeline (top)
cross-referenced ×2labeled ×2commented ×1

To OpenClaw Support Team,

I'm reporting a critical bug where the message "All quiet on my side." is being sent repeatedly in Telegram DMs despite multiple attempts to disable it through configuration. This has caused me to waste $10 in credits trying to troubleshoot and fix it.

ISSUE SUMMARY

  • Message: "All quiet on my side."
  • Frequency: Appears after almost every message sent to the bot
  • Channel: Telegram direct messages
  • Cost Impact: $0.007 per message × 30+ occurrences = $0.21+ per session
  • Total waste: ~$10 spent debugging this over multiple sessions

Root Cause

ROOT CAUSE ANALYSIS

The message appears to be generated by the silent-reply system in: /opt/homebrew/lib/node_modules/openclaw/dist/silent-reply-xG0JbFBC.js

Fix Action

Fix / Workaround

QUESTIONS FOR OPENCLAW TEAM

  1. Is there a valid configuration to completely disable silent replies?
  2. Why does silent reply trigger when explicit disables are in place?
  3. Is the message classification happening before config settings are evaluated?
  4. Can this be fixed with a patch without reinstalling?

PR fix notes

PR #78192: fix: keep Telegram DM silent fallbacks quiet

Description (problem / solution / changelog)

Fixes #78188.

Summary

  • stop synthesizing Telegram direct-message silent-reply fallback text when a turn ends with no visible final response
  • keep Telegram group/forum no-visible-response fallback behavior unchanged
  • update the Telegram dispatch regression test so DM turns remain quiet instead of delivering rewritten NO_REPLY chatter such as All quiet on my side.

Tests

  • PATH="/tmp/openclaw-pnpm-shim:$PATH" node scripts/test-projects.mjs extensions/telegram/src/bot-message-dispatch.test.ts
  • git diff --check
  • PATH="/tmp/openclaw-pnpm-shim:$PATH" npx oxfmt --check extensions/telegram/src/bot-message-dispatch.ts extensions/telegram/src/bot-message-dispatch.test.ts
  • PATH="/tmp/openclaw-pnpm-shim:$PATH" node scripts/run-oxlint.mjs --tsconfig config/tsconfig/oxlint.extensions.json extensions/telegram/src/bot-message-dispatch.ts extensions/telegram/src/bot-message-dispatch.test.ts
  • PATH="/tmp/openclaw-pnpm-shim:$PATH" node scripts/check-changed.mjs (fails only in unrelated existing diagnostics-otel lint: duplicate session.recovery.requested / session.recovery.completed case labels in extensions/diagnostics-otel/src/service.ts)

Changed files

  • extensions/telegram/src/bot-message-dispatch.test.ts (modified, +2/-7)
  • extensions/telegram/src/bot-message-dispatch.ts (modified, +2/-1)

PR #78228: fix(telegram): keep no-response DM turns quiet (no silent-reply rewrite)

Description (problem / solution / changelog)

Fixes #78188.

Root cause

dispatchTelegramMessage synthesizes a NO_REPLY reply for every turn that ends with no visible final response, which the silent-reply rewrite layer then turns into friendly chatter (e.g. "All quiet on my side.").

In groups and forum topics that's a useful signal — members can see the bot heard the mention even when it has nothing to add. In DMs it's noise: the user is the only counterpart, they already know they just sent a message that the bot decided not to reply to, and the rewritten message also burns user credits on every send. The reporter on #78188 estimated ~\$10 wasted before identifying silent-reply-xG0JbFBC.js and SILENT_REPLY_REWRITE_TEXTS as the source.

What the fix does

Gate the silent-reply NO_REPLY synthesis on isGroup. Group/forum chats keep the existing rewrite behavior (still covered by the forum-topics fallback test). DMs stay quiet when the model decides not to reply.

Tests

  • Inverted the existing rewrites a no-visible-response DM turn case in bot-message-dispatch.test.ts to assert deliverReplies is not called on DMs.
  • Added a new positive case asserting the group dispatch still triggers a silent-reply fallback when the agent emits no visible reply.

Real behavior proof

Unit tests only. Local vitest run blocked before tests by the existing @openclaw/fs-safe/config infra gap (same issue noted on recent PRs in this repo). The behavior change is a single AND-with-isGroup on the synthesis branch, exercised by both the inverted DM and the new group regression cases.

Changed files

  • extensions/telegram/src/bot-message-dispatch.test.ts (modified, +49/-3)
  • extensions/telegram/src/bot-message-dispatch.ts (modified, +7/-1)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

To OpenClaw Support Team,

I'm reporting a critical bug where the message "All quiet on my side." is being sent repeatedly in Telegram DMs despite multiple attempts to disable it through configuration. This has caused me to waste $10 in credits trying to troubleshoot and fix it.

ISSUE SUMMARY

  • Message: "All quiet on my side."
  • Frequency: Appears after almost every message sent to the bot
  • Channel: Telegram direct messages
  • Cost Impact: $0.007 per message × 30+ occurrences = $0.21+ per session
  • Total waste: ~$10 spent debugging this over multiple sessions

Steps to reproduce

REPRODUCTION

  1. Configure Telegram channel with direct message allowlist
  2. Send any message to the bot
  3. Wait a few seconds
  4. Message "All quiet on my side." appears as a separate bot message

Expected behavior

ENVIRONMENT

  • OpenClaw Version: 2026.5.2
  • OS: macOS (Darwin 25.4.0, arm64)
  • Node: v22.22.2
  • Gateway Mode: local
  • Model: openrouter/anthropic/claude-haiku-4.5
  • Channel: Telegram (direct messages)

Actual behavior

ROOT CAUSE ANALYSIS

The message appears to be generated by the silent-reply system in: /opt/homebrew/lib/node_modules/openclaw/dist/silent-reply-xG0JbFBC.js

This file contains the hardcoded string "All quiet on my side." in the SILENT_REPLY_REWRITE_TEXTS array.

The issue seems to be:

  1. Messages are being misclassified as "no reply needed"
  2. The silent reply fallback system generates this message
  3. Configuration settings to disable it are either not being read or are overridden by runtime defaults

CURRENT CONFIG (All Silent Reply Settings Removed)

{ "agents": { "defaults": { "heartbeat": { "every": "0m" } }, "list": [{ "id": "main", "name": "main" }] }, "channels": { "telegram": { "enabled": true, "dmPolicy": "allowlist", "allowFrom": ["8792194467"] } } }

IMPACT

  • Token Waste: Every unwanted message costs credits
  • User Experience: Chat is cluttered with bot-generated noise
  • Reliability: Cannot tell if bot is functioning or just spamming

OpenClaw version

OpenClaw Version: 2026.5.2

Operating system

OS: macOS (Darwin 25.4.0, arm64)

Install method

No response

Model

  • Model: openrouter/anthropic/claude-haiku-4.5

Provider / routing chain

  • Model: openrouter/anthropic/claude-haiku-4.5

Additional provider/model setup details

SUBJECT: Bug Report: Silent Reply "All quiet on my side." Message Appearing Repeatedly - $10 Wasted Debugging

To OpenClaw Support Team,

I'm reporting a critical bug where the message "All quiet on my side." is being sent repeatedly in Telegram DMs despite multiple attempts to disable it through configuration. This has caused me to waste $10 in credits trying to troubleshoot and fix it.

ISSUE SUMMARY

  • Message: "All quiet on my side."
  • Frequency: Appears after almost every message sent to the bot
  • Channel: Telegram direct messages
  • Cost Impact: $0.007 per message × 30+ occurrences = $0.21+ per session
  • Total waste: ~$10 spent debugging this over multiple sessions

ENVIRONMENT

  • OpenClaw Version: 2026.5.2
  • OS: macOS (Darwin 25.4.0, arm64)
  • Node: v22.22.2
  • Gateway Mode: local
  • Model: openrouter/anthropic/claude-haiku-4.5
  • Channel: Telegram (direct messages)

REPRODUCTION

  1. Configure Telegram channel with direct message allowlist
  2. Send any message to the bot
  3. Wait a few seconds
  4. Message "All quiet on my side." appears as a separate bot message

WHAT I TRIED (ALL FAILED)

  1. Set agents.defaults.silentReplyRewrite.direct = false → FAILED
  2. Set agents.defaults.heartbeat.every = "0m" → FAILED
  3. Completely removed silentReplyRewrite from config → FAILED
  4. Completely removed silentReply from config → FAILED
  5. Attempted to add surfaces.telegram.silentReplyRewrite → FAILED (config validation rejected)
  6. Removed extra agents (kept only main) → FAILED
  7. Removed ALL heartbeat and silent reply config → FAILED

ROOT CAUSE ANALYSIS

The message appears to be generated by the silent-reply system in: /opt/homebrew/lib/node_modules/openclaw/dist/silent-reply-xG0JbFBC.js

This file contains the hardcoded string "All quiet on my side." in the SILENT_REPLY_REWRITE_TEXTS array.

The issue seems to be:

  1. Messages are being misclassified as "no reply needed"
  2. The silent reply fallback system generates this message
  3. Configuration settings to disable it are either not being read or are overridden by runtime defaults

CURRENT CONFIG (All Silent Reply Settings Removed)

{ "agents": { "defaults": { "heartbeat": { "every": "0m" } }, "list": [{ "id": "main", "name": "main" }] }, "channels": { "telegram": { "enabled": true, "dmPolicy": "allowlist", "allowFrom": ["8792194467"] } } }

IMPACT

  • Token Waste: Every unwanted message costs credits
  • User Experience: Chat is cluttered with bot-generated noise
  • Reliability: Cannot tell if bot is functioning or just spamming

QUESTIONS FOR OPENCLAW TEAM

  1. Is there a valid configuration to completely disable silent replies?
  2. Why does silent reply trigger when explicit disables are in place?
  3. Is the message classification happening before config settings are evaluated?
  4. Can this be fixed with a patch without reinstalling?

EVIDENCE FILES

  • Detailed bug report: /Users/yuri/.openclaw/workspace/BUG_REPORT_SILENT_REPLY.md
  • Gateway logs show: [heartbeat] disabled but message still appears
  • OpenClaw version: 2026.5.2

REQUEST

Please help me:

  1. Understand why configuration disables are not working
  2. Fix this bug so the message doesn't appear
  3. Consider refunding the ~$10 wasted debugging this issue

I can provide additional logs, configuration files, or testing scenarios as needed.

Thank you, Rob Vongxay Kitchener, ON, Canada

POSTING INSTRUCTIONS

  1. GitHub Issues: https://github.com/openclaw/openclaw/issues

    • Click "New Issue"
    • Title: "Silent reply 'All quiet on my side.' appears repeatedly despite config disables"
    • Paste this entire email as the issue body

  2. Discord Community: https://discord.com/invite/clawd

    • Post in #support or #bugs channel

  3. Email (if available): Check https://github.com/openclaw/openclaw for support contact

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be mitigated by properly configuring the silent reply settings in the OpenClaw configuration file, potentially by adding a missing configuration option to explicitly disable silent replies for the Telegram channel.

Guidance

  1. Review Configuration: Verify that the configuration settings for silent replies are correctly set to disable the feature, especially for the Telegram channel. Check for any typos or incorrect syntax.
  2. Explicit Disable: Attempt to add an explicit disable for silent replies in the configuration file, specifically targeting the Telegram channel, if such an option exists.
  3. Check Documentation: Consult the OpenClaw documentation for the correct syntax and options to disable silent replies, as the current attempts may not be using the correct configuration keys.
  4. Contact Support: Reach out to the OpenClaw support team for further assistance, as they can provide more detailed guidance on configuring silent replies and potentially offer a patch or fix for the issue.

Example

No specific code example can be provided without risking inaccuracies, but ensuring the configuration file has the correct syntax and options to disable silent replies is crucial. For instance, if there's an option like silentReplyEnabled for the Telegram channel, it should be set to false.

Notes

The provided information suggests a configuration or software issue rather than a coding error. Thus, focusing on configuration adjustments and seeking support from the OpenClaw team is the most straightforward path to resolving the issue.

Recommendation

Apply a workaround by attempting to explicitly disable silent replies for the Telegram channel in the configuration file, and if unsuccessful, seek assistance from the OpenClaw support team to understand why configuration disables are not working as expected.

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

ENVIRONMENT

  • OpenClaw Version: 2026.5.2
  • OS: macOS (Darwin 25.4.0, arm64)
  • Node: v22.22.2
  • Gateway Mode: local
  • Model: openrouter/anthropic/claude-haiku-4.5
  • Channel: Telegram (direct messages)
#API middleware#SSR setup#ISR setup#authentication setup#request error

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 - ✅(Solved) Fix [Bug]: Bug Report: Silent Reply "All quiet on my side." Message Appearing Repeatedly - $10 Wasted Debugging [2 pull requests, 1 comments, 2 participants]