Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Non-compliant [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#55455•Fetched 2026-04-08 01:39:20
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
0
Author
marnimelrosemarnimelrose
Participants
barryorourkebarryorourkemarnimelrosemarnimelrose
Timeline (top)
commented ×2labeled ×2

After upgrading to 2026.3.24, agent tool calls no longer dispatch — gateway logs show only sendMessage entries with zero tool execution activity despite tools being listed as available.

Root Cause

The sandbox change in 2026.3.24 changelog ("honor tools.sandbox.tools.alsoAllow") is suspected root cause.

Fix Action

Fix / Workaround

After upgrading to 2026.3.24, agent tool calls no longer dispatch — gateway logs show only sendMessage entries with zero tool execution activity despite tools being listed as available.

Upgrade to 2026.3.24 via npm install -g openclaw@latest Send agent a task requiring tool use (e.g. create a file via obsidian-cli) (Not just Obsidian but anything) Agent acknowledges task and claims completion but no tool calls fire Gateway log shows only sendMessage entries — no tool dispatch, no sandbox deny, no errors Agent hallucinates task completion

Agent acknowledges tasks and claims completion but no tool calls are dispatched. Gateway log shows only sendMessage entries — zero tool execution activity. Agent hallucinates task completion with no actual file writes or exec calls occurring. No errors or sandbox deny entries in logs.

Code Example

Gateway log sample (all activity between agent responses — no tool dispatch entries):
{"subsystem":"gateway/channels/telegram","1":"telegram sendMessage ok chat=1139585840 message=7700"}
{"subsystem":"gateway/channels/telegram","1":"telegram sendMessage ok chat=1139585840 message=7702"}
{"subsystem":"gateway/reload","1":"config change applied (dynamic reads: tools.alsoAllow)"}

No tool dispatch, exec, write, or sandbox deny entries appear at any log level.
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading to 2026.3.24, agent tool calls no longer dispatch — gateway logs show only sendMessage entries with zero tool execution activity despite tools being listed as available.

Steps to reproduce

Upgrade to 2026.3.24 via npm install -g openclaw@latest Send agent a task requiring tool use (e.g. create a file via obsidian-cli) (Not just Obsidian but anything) Agent acknowledges task and claims completion but no tool calls fire Gateway log shows only sendMessage entries — no tool dispatch, no sandbox deny, no errors Agent hallucinates task completion

Rolled back to 2026.3.23-2 — same behavior persists due to config version mismatch warning Platform: macOS, Apple Intel Core i5, Node 25.8.0, npm global install, launchd service

Expected behavior

Agent executes tool calls (obsidian-cli write, exec, etc.) immediately when given a task, as it did prior to 2026.3.24.

Actual behavior

Agent acknowledges tasks and claims completion but no tool calls are dispatched. Gateway log shows only sendMessage entries — zero tool execution activity. Agent hallucinates task completion with no actual file writes or exec calls occurring. No errors or sandbox deny entries in logs.

OpenClaw version

2026.3.24

Operating system

Mac OS 15.7

Install method

via npm install -g openclaw@latest

Model

openai-codex/gpt-5.3-codex

Provider / routing chain

openclaw -> openai-codex (OAuth)

Additional provider/model setup details

Model: openai-codex/gpt-5.3-codex via OAuth. Auth status shows valid, 4 days remaining, 97% usage left. No API key — OAuth only. Tools confirmed listed by agent when asked. Gateway hot-reloads tools.alsoAllow config change but tool calls never appear in logs.

Logs, screenshots, and evidence

Gateway log sample (all activity between agent responses — no tool dispatch entries):
{"subsystem":"gateway/channels/telegram","1":"telegram sendMessage ok chat=1139585840 message=7700"}
{"subsystem":"gateway/channels/telegram","1":"telegram sendMessage ok chat=1139585840 message=7702"}
{"subsystem":"gateway/reload","1":"config change applied (dynamic reads: tools.alsoAllow)"}

No tool dispatch, exec, write, or sandbox deny entries appear at any log level.

Impact and severity

Affected: Single-user Telegram setup on macOS, npm global install Severity: Critical — blocks all tool execution, agent is non-functional Frequency: 100% — every tool call attempt fails silently Consequence: Agent hallucinates task completion, no files written, no execs run. Complete loss of agentic capability post-upgrade.

Additional information

Last known good version: 2026.3.13 (tools executed correctly) First known bad version: 2026.3.24 Attempted mitigations (none resolved):

Added tools.alsoAllow globally and per-agent Rolled back to 2026.3.23-2 (config version mismatch warning persists) Multiple /reset and /new session resets NODE_OPTIONS=--dns-result-order=ipv4first confirmed present in plist Agent lists all tools as available when asked, but zero tool calls appear in gateway logs

The sandbox change in 2026.3.24 changelog ("honor tools.sandbox.tools.alsoAllow") is suspected root cause.

extent analysis

Fix Plan

To resolve the issue of agent tool calls not dispatching after upgrading to 2026.3.24, follow these steps:

  1. Revert the tools.sandbox.tools.alsoAllow change: Since the sandbox change in 2026.3.24 is suspected to be the root cause, try reverting this change.
  2. Update tools.alsoAllow configuration: Ensure that tools.alsoAllow is properly configured globally and per-agent.
  3. Reset agent and gateway: Perform a /reset and /new session reset to ensure a clean state.

Example configuration update:

{
  "tools": {
    "alsoAllow": ["obsidian-cli", "exec"]
  }
}

Example code snippet to update configuration:

const config = require('./config.json');
config.tools.alsoAllow = ['obsidian-cli', 'exec'];
require('fs').writeFileSync('./config.json', JSON.stringify(config, null, 2));

Verification

To verify that the fix worked:

  1. Check the gateway logs for tool dispatch entries.
  2. Send a task to the agent requiring tool use (e.g., create a file via obsidian-cli).
  3. Verify that the tool call is executed and the task is completed successfully.

Extra Tips

  • Ensure that the tools.alsoAllow configuration is properly updated and applied.
  • If issues persist, try rolling back to a previous version (e.g., 2026.3.13) to confirm the fix.
  • Monitor the gateway logs for any errors or issues related to 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

Agent executes tool calls (obsidian-cli write, exec, etc.) immediately when given a task, as it did prior to 2026.3.24.

#api#model download#tokenizer error#prompt formatting#chain error

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]: Non-compliant [2 comments, 2 participants]