Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Telegram channel renders intermediate tool call steps as visible messages [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#71575•Fetched 2026-04-26 05:11:17
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
adamwdearadamwdear
Participants
adamwdearadamwdear

When an agent is running in a Telegram-bound session and executes tool calls (e.g. exec, memory_search, etc.), the intermediate "Working…" status updates and raw tool output are rendered as visible messages in the Telegram chat. Only the final assistant reply should be delivered to the user.

Root Cause

When an agent is running in a Telegram-bound session and executes tool calls (e.g. exec, memory_search, etc.), the intermediate "Working…" status updates and raw tool output are rendered as visible messages in the Telegram chat. Only the final assistant reply should be delivered to the user.

Code Example

Working…
• command search "telegram.*tool|tool.*leak|leaking|tool call.*telegram|telegram.*leak" in 2>/dev/null -> show first 20 lines, grep -r ...
• tool: exec
• exec search "telegram.*tool|tool.*leak|leaking|tool call.*telegram|telegram.*leak" in 2>/dev/null -> show first 20 lines...
• /Users/.../memory/2026-03-15.md:- Brendan: Essentially clone of Sam — Telegram bot...
• tool: exec
• (same exec entry repeated)
RAW_BUFFERClick to expand / collapse

Description

When an agent is running in a Telegram-bound session and executes tool calls (e.g. exec, memory_search, etc.), the intermediate "Working…" status updates and raw tool output are rendered as visible messages in the Telegram chat. Only the final assistant reply should be delivered to the user.

Expected behavior

  • User sees only the final assistant message
  • Tool call execution, working indicators, and raw output remain internal/invisible

Actual behavior

  • Telegram receives and displays messages like:
    • Working… • command search "..." → exec
    • Raw tool result output (shell output, file paths, etc.)
    • Duplicate entries for the same tool call step

Example of leaked output received by the user in Telegram:

Working…
• command search "telegram.*tool|tool.*leak|leaking|tool call.*telegram|telegram.*leak" in 2>/dev/null -> show first 20 lines, grep -r ...
• tool: exec
• exec search "telegram.*tool|tool.*leak|leaking|tool call.*telegram|telegram.*leak" in 2>/dev/null -> show first 20 lines...
• /Users/.../memory/2026-03-15.md:- Brendan: Essentially clone of Sam — Telegram bot...
• tool: exec
• (same exec entry repeated)

Environment

  • Channel: Telegram (direct chat)
  • OpenClaw version: 2026.4.23
  • Model: anthropic/claude-sonnet-4-6
  • Reproducible: Yes — happens during multi-step tool use in Telegram sessions

extent analysis

TL;DR

Filter or suppress intermediate "Working…" status updates and raw tool output in Telegram-bound sessions to prevent unwanted message visibility.

Guidance

  • Investigate the message handling logic in the OpenClaw version 2026.4.23 to identify where intermediate status updates and raw tool output are being sent to the Telegram chat.
  • Check for any configuration options or flags that can be used to suppress or filter these messages, ensuring only the final assistant reply is delivered to the user.
  • Consider implementing a message filtering mechanism to exclude messages containing specific keywords like "Working…" or "tool:" to prevent them from being sent to the user.
  • Review the tool call execution workflow to determine why duplicate entries for the same tool call step are being generated and displayed.

Example

No code snippet can be provided without more context on the OpenClaw codebase, but an example of how message filtering might work could involve checking the content of messages before sending them to the Telegram chat:

if "Working…" not in message and not message.startswith("tool:"):
    # Send message to Telegram chat

Notes

The provided solution assumes that the issue lies within the OpenClaw application's handling of messages in Telegram-bound sessions. Without access to the OpenClaw codebase or more detailed documentation, it's challenging to provide a precise fix.

Recommendation

Apply a workaround by filtering or suppressing intermediate messages until a more permanent solution can be integrated into the OpenClaw application, as the root cause of the issue is not immediately clear without 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

  • User sees only the final assistant message
  • Tool call execution, working indicators, and raw output remain internal/invisible
#prompt formatting#chain error#conversation history#tool integration#LLM response

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 Telegram channel renders intermediate tool call steps as visible messages [1 participants]