Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Bundled ACPX extension missing plugin-local acpx/codex-acp binaries after 2026.4.26 update [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#73833•Fetched 2026-04-29 06:14:28
View on GitHub
Comments
2
Participants
2
Timeline
3
Reactions
0
Author
only21milonly21mil
Participants
clawsweeper[bot]clawsweeper[bot]only21milonly21mil
Timeline (top)
commented ×2closed ×1

Root Cause

After updating to OpenClaw 2026.4.26, ACP/Codex runtime spawn can be unavailable because the bundled ACPX extension points at a plugin-local codex-acp binary that is not installed/staged.

Code Example

/opt/homebrew/lib/node_modules/openclaw/dist/extensions/acpx/node_modules/.bin/codex-acp

---

ls: /opt/homebrew/lib/node_modules/openclaw/dist/extensions/acpx/node_modules/.bin/codex-acp: No such file or directory
ls: /opt/homebrew/lib/node_modules/openclaw/dist/extensions/acpx/node_modules/.bin/acpx: No such file or directory

---

{
  "name": "@openclaw/acpx",
  "version": "2026.4.25",
  "dependencies": {
    "acpx": "0.6.1"
  }
}

---

/opt/homebrew/lib/node_modules/openclaw/dist/extensions/acpx/node_modules/.bin/acpx
/opt/homebrew/lib/node_modules/openclaw/dist/extensions/acpx/node_modules/.bin/codex-acp
RAW_BUFFERClick to expand / collapse

Bug

After updating to OpenClaw 2026.4.26, ACP/Codex runtime spawn can be unavailable because the bundled ACPX extension points at a plugin-local codex-acp binary that is not installed/staged.

Local evidence

OpenClaw config points Codex ACP at:

/opt/homebrew/lib/node_modules/openclaw/dist/extensions/acpx/node_modules/.bin/codex-acp

But on the updated install:

ls: /opt/homebrew/lib/node_modules/openclaw/dist/extensions/acpx/node_modules/.bin/codex-acp: No such file or directory
ls: /opt/homebrew/lib/node_modules/openclaw/dist/extensions/acpx/node_modules/.bin/acpx: No such file or directory

The bundled extension declares the dependency:

{
  "name": "@openclaw/acpx",
  "version": "2026.4.25",
  "dependencies": {
    "acpx": "0.6.1"
  }
}

But the plugin-local runtime dependency is missing. A global acpx may exist, but it can be stale and should not be used as the bundled runtime source of truth. In my environment global acpx is 0.3.0 while the bundled plugin expects 0.6.1.

Expected behavior

When OpenClaw ships/enables the bundled @openclaw/acpx extension and config points ACP agents at plugin-local binaries, update/startup/doctor should ensure the pinned plugin-local runtime dependency is installed/staged before ACP runtime is marked healthy.

At minimum, openclaw doctor --fix or gateway ACP runtime startup should detect and repair/clearly report:

  • missing dist/extensions/acpx/node_modules/.bin/acpx
  • missing dist/extensions/acpx/node_modules/.bin/codex-acp
  • plugin-local ACPX version mismatch versus dist/extensions/acpx/package.json

Actual impact

ACP/Codex background worker routing falls back to native/subagent execution because the configured ACP wrapper is unavailable.

Suggested fix

During bundled plugin runtime-dependency staging, install/link/copy the pinned acpx dependency for @openclaw/acpx so these exist after update:

/opt/homebrew/lib/node_modules/openclaw/dist/extensions/acpx/node_modules/.bin/acpx
/opt/homebrew/lib/node_modules/openclaw/dist/extensions/acpx/node_modules/.bin/codex-acp

Then include a smoke/doctor check that validates the configured ACP agent command path exists and is executable.

extent analysis

TL;DR

The most likely fix is to install or link the pinned acpx dependency for @openclaw/acpx during bundled plugin runtime-dependency staging.

Guidance

  • Verify the existence and version of acpx in the global environment and compare it with the version expected by the bundled plugin (0.6.1) to ensure compatibility.
  • Check the package.json file of @openclaw/acpx to confirm the dependency version and ensure it matches the expected version.
  • Consider running a command like npm install or yarn install in the dist/extensions/acpx directory to install the missing dependencies.
  • Implement a smoke/doctor check to validate the existence and executability of the configured ACP agent command path.

Example

No code snippet is provided as the issue is more related to dependency management and configuration.

Notes

The suggested fix assumes that the acpx dependency is correctly declared in the package.json file of @openclaw/acpx. If the issue persists, further investigation into the dependency management and installation process may be necessary.

Recommendation

Apply the suggested fix by installing or linking the pinned acpx dependency during bundled plugin runtime-dependency staging, as this directly addresses the identified issue of missing dependencies.

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

When OpenClaw ships/enables the bundled @openclaw/acpx extension and config points ACP agents at plugin-local binaries, update/startup/doctor should ensure the pinned plugin-local runtime dependency is installed/staged before ACP runtime is marked healthy.

At minimum, openclaw doctor --fix or gateway ACP runtime startup should detect and repair/clearly report:

  • missing dist/extensions/acpx/node_modules/.bin/acpx
  • missing dist/extensions/acpx/node_modules/.bin/codex-acp
  • plugin-local ACPX version mismatch versus dist/extensions/acpx/package.json
#agent execution#network issue#logging issue#authentication issue#prompt issue

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]: Bundled ACPX extension missing plugin-local acpx/codex-acp binaries after 2026.4.26 update [2 comments, 2 participants]