Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Regression: Telegram topic leaks raw tool_uses JSON before final answer on 2026.4.23 [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#71475•Fetched 2026-04-26 05:12:27
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
bogdanovichbogdanovich
Participants
bogdanovichbogdanovichsteipetesteipete
Timeline (top)
closed ×1commented ×1

OpenClaw 2026.4.23 can still leak raw internal tool-call wrapper JSON into a Telegram forum topic before sending the normal final answer.

This appears related to #59150 / #59643 and #52084, but it reproduces after the phase-separation fix landed.

Root Cause

  • #59150
  • #59643
  • #52084
  • #25592
  • #60179 is similar in surface symptoms but different root cause: there tools were not executed.

Code Example

{"tool_uses":[{"recipient_name":"functions.inventorydb__list_items","parameters":{"query":"...","limit":20}}]}
RAW_BUFFERClick to expand / collapse

Summary

OpenClaw 2026.4.23 can still leak raw internal tool-call wrapper JSON into a Telegram forum topic before sending the normal final answer.

This appears related to #59150 / #59643 and #52084, but it reproduces after the phase-separation fix landed.

Environment

  • OpenClaw: 2026.4.23 (a979721)
  • Channel: Telegram forum topic
  • Runtime model: openai-codex/gpt-5.4
  • Tools involved: MCP tool calls
  • OS: Linux 6.17.0-22-generic x64
  • Node: 22.22.2

Symptom

A user asked a normal inventory lookup question. Telegram received a visible message like:

{"tool_uses":[{"recipient_name":"functions.inventorydb__list_items","parameters":{"query":"...","limit":20}}]}

Then OpenClaw sent the correct natural-language final answer.

Expected

Raw tool routing payloads should never be sent to user-visible channels.

Actual

The raw tool_uses wrapper was delivered as a separate Telegram message before the final answer.

Why this is not the same as "tools not executed"

The tool calls did execute successfully, and the final answer used the tool results. The bug is that the raw tool-call wrapper also leaked to the channel.

Related

  • #59150
  • #59643
  • #52084
  • #25592
  • #60179 is similar in surface symptoms but different root cause: there tools were not executed.

Notes

The concrete local transcript includes private user/channel and inventory data, so this report intentionally uses a sanitized reproduction snippet. The important distinguishing feature is that the leaked message is a raw tool_uses wrapper, while the same turn still proceeds to execute tools and send a normal final answer.

extent analysis

TL;DR

Review and update the tool-call wrapper handling in OpenClaw 2026.4.23 to prevent leaking raw internal JSON into user-visible channels.

Guidance

  • Investigate the phase-separation fix from #59150, #59643, and #52084 to ensure it correctly handles tool-call wrappers in the Telegram forum topic channel.
  • Verify that the tool_uses wrapper is properly filtered or removed before sending messages to the user-visible channel.
  • Check the logging and monitoring setup to detect similar issues in the future, focusing on the interaction between OpenClaw, the openai-codex/gpt-5.4 runtime model, and the Telegram channel.
  • Consider adding a sanitization step for outgoing messages to prevent sensitive data leaks.

Example

No specific code snippet can be provided without more context, but the fix likely involves modifying the message processing pipeline to exclude or transform the tool_uses wrapper.

Notes

The provided information suggests a complex interaction between OpenClaw, the runtime model, and the Telegram channel. Without more details on the internal workings of OpenClaw and its tool-call wrapper handling, the guidance is focused on general troubleshooting and verification steps.

Recommendation

Apply a workaround to filter or remove the tool_uses wrapper from outgoing messages until a permanent fix can be implemented, as the issue appears to be related to the handling of internal tool-call wrappers in user-visible channels.

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…
#retrieval issue#search optimization#API routing#API middleware#SSR setup

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 Regression: Telegram topic leaks raw tool_uses JSON before final answer on 2026.4.23 [1 comments, 2 participants]