openclaw - 💡(How to fix) Fix [Bug]: Sub-agent exec tool calls broken after update to 2026.4.8 [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#63422Fetched 2026-04-09 07:53:58
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×1subscribed ×1

After updating from 2026.4.5 to 2026.4.8, all sub-agents lost the ability to execute exec tool calls against canonical data files — they reported being unable to find files that were accessible to the main agent in the same session.

Error Message

Sub-agents report they cannot find canonical data files that are accessible to the main agent in the same session. Example response: "I can't find the file in the workspace." The main agent can execute identical jq commands against the same files successfully. All sub-agents affected. No error in gateway logs — sub-agents simply fail to resolve file paths via exec.

Root Cause

After updating from 2026.4.5 to 2026.4.8, all sub-agents lost the ability to execute exec tool calls against canonical data files — they reported being unable to find files that were accessible to the main agent in the same session.

Fix Action

Fix / Workaround

Affected: User with sub-agents configured using exec tool access. Severity: High — completely blocks sub-agent functionality. All sub-agents unable to execute exec calls. Only workaround is rollback to 2026.4.5. Frequency: 100% reproducible — occurs on every sub-agent exec call after updating to 2026.4.8. Consequence: Full rollback to previous version required to restore functionality. No partial workaround available.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After updating from 2026.4.5 to 2026.4.8, all sub-agents lost the ability to execute exec tool calls against canonical data files — they reported being unable to find files that were accessible to the main agent in the same session.

Steps to reproduce

  1. Install OpenClaw 2026.4.8 (upgrade from 2026.4.5).
  2. Configure one or more sub-agents with exec tool access to canonical data files via jq.
  3. Delegate a query to any sub-agent that requires an exec/jq call.
  4. Observe sub-agent reports it cannot find the canonical data file, despite the file being accessible to the main agent in the same session.
  5. Roll back to 2026.4.5 — sub-agent exec calls work correctly immediately.

Expected behavior

Sub-agents should execute exec tool calls against canonical data files as they did in 2026.4.5. The main agent retained full exec access throughout — only sub-agent sessions were affected. Rolling back to 2026.4.5 (3e72c03) restored full sub-agent exec functionality immediately.

Actual behavior

Sub-agents report they cannot find canonical data files that are accessible to the main agent in the same session. Example response: "I can't find the file in the workspace." The main agent can execute identical jq commands against the same files successfully. All sub-agents affected. No error in gateway logs — sub-agents simply fail to resolve file paths via exec.

OpenClaw version

2026.4.8 (9ece252) — broken, 2026.4.5 (3e72c03) — working

Operating system

macOS 15.4

Install method

npm global

Model

openai-codex/gpt-5.4 (main agent), openai/gpt-5.4-nano (sub-agents)

Provider / routing chain

openclaw -> openai-codex (OAuth), [main agent] openclaw -> openai API, [sub-agents] openclaw -> ollama (local, socat relay) [sub-agents fallback]

Additional provider/model setup details

Sub-agents are configured with per-agent model overrides via environment variable substitution in openclaw.json. Main agent uses openai-codex OAuth. Sub-agents use openai API key for primary and local Ollama via socat relay for fallback. exec approval mode is "targets" with all sub-agent IDs explicitly listed in agentFilter. Bug is model-agnostic — occurs regardless of which model is assigned to sub-agents.

Logs, screenshots, and evidence

Impact and severity

Affected: User with sub-agents configured using exec tool access. Severity: High — completely blocks sub-agent functionality. All sub-agents unable to execute exec calls. Only workaround is rollback to 2026.4.5. Frequency: 100% reproducible — occurs on every sub-agent exec call after updating to 2026.4.8. Consequence: Full rollback to previous version required to restore functionality. No partial workaround available.

Additional information

No response

extent analysis

TL;DR

Rolling back to OpenClaw version 2026.4.5 resolves the issue where sub-agents cannot execute exec tool calls against canonical data files.

Guidance

  • Verify that the issue is specific to version 2026.4.8 by testing other versions to confirm the regression.
  • Check the configuration of sub-agents and exec tool access to ensure that no changes were made during the upgrade process.
  • Test the main agent's exec access to confirm that the issue is isolated to sub-agents.
  • Consider reporting the issue to the OpenClaw developers or community for further assistance and to track any potential fixes.

Example

No code snippet is provided as the issue is related to a specific version of OpenClaw and its configuration.

Notes

The issue seems to be a regression introduced in version 2026.4.8, and rolling back to the previous version resolves the issue. However, this may not be a viable long-term solution, and further investigation or reporting to the OpenClaw developers may be necessary.

Recommendation

Apply workaround: Roll back to OpenClaw version 2026.4.5, as it is the only known solution to restore sub-agent exec functionality. This is due to the high severity and 100% reproducibility of the issue in version 2026.4.8.

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

Sub-agents should execute exec tool calls against canonical data files as they did in 2026.4.5. The main agent retained full exec access throughout — only sub-agent sessions were affected. Rolling back to 2026.4.5 (3e72c03) restored full sub-agent exec functionality immediately.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING