openclaw - 💡(How to fix) Fix [Bug]: Tool calls not executing after upgrade to 2026.4.1 - displayed as plain text instead [5 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#59827Fetched 2026-04-08 02:40:02
View on GitHub
Comments
5
Participants
4
Timeline
23
Reactions
0
Timeline (top)
mentioned ×8subscribed ×8commented ×5labeled ×2

After upgrading to OpenClaw 2026.4.1, all tool calls are displayed as plain text in responses instead of being executed by the system.

Root Cause

After upgrading to OpenClaw 2026.4.1, all tool calls are displayed as plain text in responses instead of being executed by the system.

Code Example

[tool_use id=toolu1a2b3c4d5e6f7a8b9c0d1e2f name=exec]
{"command": "hostname", "timeout": "10"}

---

Tool call output displayed as text:
[tool_use id=toolu1a2b3c4d5e6f7a8b9c0d1e2f name=exec]
{"command": "hostname", "timeout": "10"}

Tool configuration (verified):
{
  "profile": "coding",
  "sessions": {"visibility": "all"},
  "agentToAgent": {"enabled": true},
  "exec": {"security": "full", "host": "gateway", "ask": "off"},
  "fs": {"workspaceOnly": false}
}
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading to OpenClaw 2026.4.1, all tool calls are displayed as plain text in responses instead of being executed by the system.

Steps to reproduce

  1. Upgrade OpenClaw to version 2026.4.1
  2. Start any agent session
  3. Attempt to call any tool (exec, read, web_search, etc.)
  4. Observe tool call syntax displayed as plain text in response, e.g.:
[tool_use id=toolu1a2b3c4d5e6f7a8b9c0d1e2f name=exec]
{"command": "hostname", "timeout": "10"}
  1. Tool does not execute, no result returned

Expected behavior

Tool calls should be parsed by the OpenClaw system and executed, returning tool results to the agent for processing.

Actual behavior

Tool calls are displayed as plain text in the assistant's response. Multiple tool types affected (exec, read, web_search). Verified tool configuration is correct: exec.security="full", exec.host="gateway", exec.ask="off".

OpenClaw version

2026.4.1

Operating system

Ubuntu 24.04 (Linux 5.15.0-171-generic x64)

Install method

npm global

Model

bailian-coding-plan/qwen3.5-plus

Provider / routing chain

openclaw -> bailian-coding-plan -> qwen3.5-plus

Additional provider/model setup details

Default model is bailian-coding-plan/qwen3.5-plus. Tool configuration profile is set to "coding". agentToAgent is enabled with multiple agents allowed. This issue affects all tool types regardless of model or routing.

Logs, screenshots, and evidence

Tool call output displayed as text:
[tool_use id=toolu1a2b3c4d5e6f7a8b9c0d1e2f name=exec]
{"command": "hostname", "timeout": "10"}

Tool configuration (verified):
{
  "profile": "coding",
  "sessions": {"visibility": "all"},
  "agentToAgent": {"enabled": true},
  "exec": {"security": "full", "host": "gateway", "ask": "off"},
  "fs": {"workspaceOnly": false}
}

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The most likely fix for the issue of tool calls being displayed as plain text in OpenClaw 2026.4.1 is to revert to a previous version or wait for a patch, as the current version seems to have a regression bug affecting tool execution.

Guidance

  • Verify that the issue persists across different models and routing chains to confirm it's a global problem with OpenClaw 2026.4.1.
  • Check the OpenClaw changelog or release notes for version 2026.4.1 to see if there are any known issues or regressions related to tool execution.
  • Consider downgrading to the previous version of OpenClaw to restore functionality until a fix is available for version 2026.4.1.
  • Monitor the OpenClaw community or support channels for any updates or temporary workarounds for this issue.

Example

No specific code example can be provided without more details on the internal workings of OpenClaw or its API, but checking the tool configuration and ensuring it matches the expected format might be useful:

{
  "profile": "coding",
  "sessions": {"visibility": "all"},
  "agentToAgent": {"enabled": true},
  "exec": {"security": "full", "host": "gateway", "ask": "off"},
  "fs": {"workspaceOnly": false}
}

Notes

The exact cause of the regression is not specified in the issue, so these suggestions are based on the information provided. It's possible that the issue is specific to certain configurations or environments.

Recommendation

Apply workaround: Downgrade to the previous version of OpenClaw until a fix is released for version 2026.4.1, as this version seems to introduce a regression affecting tool execution.

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 should be parsed by the OpenClaw system and executed, returning tool results to the agent for processing.

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 [Bug]: Tool calls not executing after upgrade to 2026.4.1 - displayed as plain text instead [5 comments, 4 participants]