Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] v2026.4.22: Tool calls leak as visible XML/bracket text on all models [2 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#70331•Fetched 2026-04-23 07:26:12
View on GitHub
Comments
2
Participants
2
Timeline
3
Reactions
0
Author
xiaobai-khhomexiaobai-khhome
Participants
rafiki270rafiki270xiaobai-khhomexiaobai-khhome
Timeline (top)
commented ×2closed ×1

After upgrading to v2026.4.22 (274 new commits pulled 2026-04-22 ~00:25 PDT), all tool calls leak as visible text in chat delivery instead of being intercepted and executed by the gateway.

Root Cause

After upgrading to v2026.4.22 (274 new commits pulled 2026-04-22 ~00:25 PDT), all tool calls leak as visible text in chat delivery instead of being intercepted and executed by the gateway.

Fix Action

Workaround

Rolled back to v2026.4.20 (commit 7b1871b99bd7), issue fully resolved.

cd ~/openclaw
git reset --hard 7b1871b99bd7
pnpm install && pnpm build && pnpm ui:build
sudo npm install -g .
sudo systemctl restart openclaw-gateway

Code Example

cd ~/openclaw
git reset --hard 7b1871b99bd7
pnpm install && pnpm build && pnpm ui:build
sudo npm install -g .
sudo systemctl restart openclaw-gateway
RAW_BUFFERClick to expand / collapse

Summary

After upgrading to v2026.4.22 (274 new commits pulled 2026-04-22 ~00:25 PDT), all tool calls leak as visible text in chat delivery instead of being intercepted and executed by the gateway.

Affected formats observed

  • MiniMax M2.7: [TOOL_CALL] {tool => 'exec', args => {--command "echo test"}} [/TOOL_CALL]
  • DeepSeek Chat / Sonnet 4.6: <function_calls><invoke name="read"><parameter name="path">...</parameter></invoke></function_calls>

Affected models

All tested models exhibit the regression:

  • minimax/MiniMax-M2.7 (direct)
  • deepseek/deepseek-chat
  • anthropic/claude-sonnet-4-6

Steps to reproduce

  1. Upgrade from v2026.4.20 → v2026.4.22 (via daily timer)
  2. Send any message via Telegram that triggers a tool call
  3. Tool call XML/bracket text appears verbatim in the Telegram reply instead of being executed

Expected behavior

Tool calls are intercepted by the gateway, executed, and results returned to the model — never visible in delivery output.

Workaround

Rolled back to v2026.4.20 (commit 7b1871b99bd7), issue fully resolved.

cd ~/openclaw
git reset --hard 7b1871b99bd7
pnpm install && pnpm build && pnpm ui:build
sudo npm install -g .
sudo systemctl restart openclaw-gateway

Environment

  • Platform: Native Linux (Ubuntu 25.10)
  • Gateway: v2026.4.22 (broken) / v2026.4.20 (working)
  • Channel: Telegram

Related issues

  • #57868 (Tool call XML leaking into Discord messages)
  • #60179 (Tool calls returned as raw text in 2026.4.2)

extent analysis

TL;DR

Reverting to version v2026.4.20 resolves the issue where tool calls are not intercepted by the gateway and appear as visible text in chat delivery.

Guidance

  • Review the changes introduced in the 274 new commits pulled on 2026-04-22 to identify potential causes for the regression.
  • Verify that the issue is specific to the Telegram channel by testing tool calls through other channels.
  • Check the gateway logs for any errors or warnings related to tool call processing to understand why the interception is failing.
  • Consider applying the workaround provided, which involves rolling back to version v2026.4.20, until a fix is available for version v2026.4.22.

Example

No specific code snippet is provided as the issue seems to be related to a version regression rather than a code-level problem.

Notes

The issue seems to be specific to version v2026.4.22, and rolling back to v2026.4.20 resolves the problem. However, this might not be a viable long-term solution, and further investigation into the changes introduced in v2026.4.22 is necessary to find a permanent fix.

Recommendation

Apply the workaround by rolling back to version v2026.4.20, as it is a known stable version that does not exhibit the tool call leakage issue, allowing for continued functionality until a fixed version of v2026.4.22 or later is released.

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

Tool calls are intercepted by the gateway, executed, and results returned to the model — never visible in delivery output.

#model save/load#optimization#mixed precision#training loop#device allocation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING