Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Telegram direct chat still leaks internal assistant dialogue / commentary into user-visible messages [3 comments, 4 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#59995•Fetched 2026-04-08 02:37:47
View on GitHub
Comments
3
Participants
4
Timeline
4
Reactions
0
Author
novaflash82novaflash82
Participants
garadun1-cmykgaradun1-cmykmbelinkymbelinkynovaflash82novaflash82tlnini-afktlnini-afk
Timeline (top)
commented ×3closed ×1

OpenClaw is still leaking internal assistant dialogue / commentary into Telegram direct chat in a fresh session, even with reasoning off. This includes internal-looking planning text and tool-orchestration style output that should never be user-visible.

This appears to be part of the broader "intermediate assistant text leaks to channel" bug family, but I'm filing this report because it is still happening after newer updates and the user-facing symptom remains severe.

Root Cause

This appears to be part of the broader "intermediate assistant text leaks to channel" bug family, but I'm filing this report because it is still happening after newer updates and the user-facing symptom remains severe.

RAW_BUFFERClick to expand / collapse

Summary

OpenClaw is still leaking internal assistant dialogue / commentary into Telegram direct chat in a fresh session, even with reasoning off. This includes internal-looking planning text and tool-orchestration style output that should never be user-visible.

This appears to be part of the broader "intermediate assistant text leaks to channel" bug family, but I'm filing this report because it is still happening after newer updates and the user-facing symptom remains severe.

What happened

In a direct Telegram conversation, internal-looking assistant text leaked into chat instead of only the final user-facing response.

The user described it as my internal dialogue leaking through. The visible symptom matches previously reported cases where OpenClaw forwards commentary/planning/intermediate text instead of suppressing it.

Expected behavior

Only the final intentional assistant reply should reach the Telegram user.

The following should never be visible in chat:

  • internal planning/checklist text
  • commentary-phase text
  • tool orchestration traces
  • partial/non-final assistant text
  • reasoning-like or internal dialogue text

Actual behavior

Telegram users can still see internal/non-final assistant output in normal chat flow.

Repro hints

This seems most likely during:

  1. Telegram direct chat
  2. Multi-step tasks involving tool calls
  3. Fresh sessions / newly reset sessions
  4. Cases where the assistant emits any commentary/planning text before the final answer

Why this is still worth reporting

There are existing related issues, but this confirms the bug is still user-visible in current real-world Telegram usage after newer updates.

Related issues

Likely related to:

  • #52084 — Telegram/Codex commentary-phase tool-call trace leak
  • #25592 — Text between tool calls leaks to messaging channels
  • #46554 — Internal assistant planning text leaks to user chat even with verbose off
  • #58066 — Internal commentary snippets intermittently leak into replies
  • #59536 — Aborted/timeout runs can leak internal partial assistant content

If maintainers prefer, this can be closed as a duplicate of the best canonical issue.

Environment

  • Channel: Telegram DM
  • Session type: normal direct chat
  • Reasoning: off
  • Version: current recent update line (observed on a newly updated install)
  • Runtime in affected session: OpenClaw main chat flow

I can provide sanitized examples or exact visible leak text if needed.

extent analysis

TL;DR

The issue can be mitigated by reviewing and refining the text filtering logic in the OpenClaw chat flow to prevent internal dialogue and commentary from leaking into Telegram direct chats.

Guidance

  • Review the related issues (#52084, #25592, #46554, #58066, #59536) to understand the historical context and potential causes of the text leakage.
  • Investigate the text filtering logic in the OpenClaw chat flow to identify why internal dialogue and commentary are not being suppressed as expected.
  • Consider adding additional logging or debugging statements to capture the exact text being leaked and the circumstances under which it occurs.
  • Evaluate the impact of the "reasoning off" setting on the text filtering logic and whether it is being correctly applied in all cases.

Example

No code snippet is provided due to the lack of specific technical details in the issue.

Notes

The issue appears to be related to a broader family of bugs, and resolving it may require a comprehensive review of the text filtering logic and chat flow in OpenClaw.

Recommendation

Apply a workaround by refining the text filtering logic to prevent internal dialogue and commentary from leaking into Telegram direct chats, as the root cause of the issue is not immediately clear and may require further investigation.

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

Only the final intentional assistant reply should reach the Telegram user.

The following should never be visible in chat:

  • internal planning/checklist text
  • commentary-phase text
  • tool orchestration traces
  • partial/non-final assistant text
  • reasoning-like or internal dialogue text
#serialization error#model compatibility#GPU setup#container setup#orchestration issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING