openclaw - ✅(Solved) Fix [Bug] 2026.3.13 Windows: ACP runtime unavailable after update — acpx 0.3.0 vs pinned 0.1.16, expectedVersion:any workaround not effective [1 pull requests, 2 comments, 3 participants]

Q: Expected behavior

Either the bundled acpx version matches `ACPX_PINNED_VERSION`, or `expectedVersion: "any"` should fully bypass all version/binary checks and allow the plugin to initialize normally.

openclaw2026-03-21 06:39:40

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#51468•Fetched 2026-04-08 01:10:48

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Participants

Assignees

Timeline (top)

commented ×2assigned ×1cross-referenced ×1mentioned ×1

After upgrading to OpenClaw 2026.3.13 on Windows, the ACP runtime backend is unavailable. This appears to be a recurrence of #43997, but with two compounding issues specific to Windows.

Error Message

Error 1 — Windows .cmd wrapper not resolvable: Error 2 — After plugin-local reinstall, version mismatch:

Root Cause

After upgrading to OpenClaw 2026.3.13 on Windows, the ACP runtime backend is unavailable. This appears to be a recurrence of #43997, but with two compounding issues specific to Windows.

Fix Action

Fix / Workaround

Workarounds attempted (none resolved the issue)

PR fix notes

PR #51867: fix(acpx): align pinned version with bundled 0.3.0 and wrapper fallback

Repository: openclaw/openclaw
Author: shashb27
State: closed | merged: False
Link: https://github.com/openclaw/openclaw/pull/51867

Description (problem / solution / changelog)

Fixes #51468

Summary

This addresses the Windows ACP runtime regression where:

ACPX_PINNED_VERSION remained at

Changed files

extensions/acpx/src/config.ts (modified, +1/-1)
extensions/acpx/src/ensure.ts (modified, +103/-2)

Code Example

acpx local binary unavailable or mismatched (acpx.cmd wrapper resolved, 
but no executable/Node entrypoint could be resolved without shell execution.)
; running plugin-local install

---

acpx runtime setup failed: plugin-local acpx verification failed after install: 
acpx version mismatch: found 0.3.0, expected 0.1.16

RAW_BUFFERClick to expand / collapse

Summary

After upgrading to OpenClaw 2026.3.13 on Windows, the ACP runtime backend is unavailable. This appears to be a recurrence of #43997, but with two compounding issues specific to Windows.

Environment

OpenClaw: 2026.3.13
OS: Windows 11 (10.0.26200 x64)
Node: v24.14.0
acpx bundled version: 0.3.0
ACPX_PINNED_VERSION (expected by plugin): 0.1.16

Errors in gateway log

Error 1 — Windows .cmd wrapper not resolvable:

acpx local binary unavailable or mismatched (acpx.cmd wrapper resolved, 
but no executable/Node entrypoint could be resolved without shell execution.)
; running plugin-local install

Error 2 — After plugin-local reinstall, version mismatch:

acpx runtime setup failed: plugin-local acpx verification failed after install: 
acpx version mismatch: found 0.3.0, expected 0.1.16

Steps to reproduce

Run openclaw update on Windows (fails with EBUSY — gateway holds file lock on openclaw node_modules dir)
Stop gateway, run npm install -g openclaw@latest --force, restart gateway
ACP backend reports unavailable on all sessions_spawn with runtime: "acp"

Workarounds attempted (none resolved the issue)

Set plugins.entries.acpx.config.expectedVersion: "any" — version gate bypassed per log, but plugin still fails to register
Set plugins.entries.acpx.config.command to direct path ...\acpx\dist\cli.js — no effect
Set plugins.entries.acpx.config.strictWindowsCmdWrapper: false — no effect
Multiple gateway stop/starts — no effect

Relationship to #43997

This is the same version mismatch bug recurring. PR #47231 updated the pin to 0.2.0 to fix #43997, but 2026.3.13 now ships with 0.3.0 and the pin appears to still be 0.1.16. Additionally on Windows the .cmd wrapper resolution issue compounds the problem even when expectedVersion: any is set.

Expected behavior

Either the bundled acpx version matches ACPX_PINNED_VERSION, or expectedVersion: "any" should fully bypass all version/binary checks and allow the plugin to initialize normally.

extent analysis

Fix Plan

To resolve the issue, we need to address the version mismatch and the Windows .cmd wrapper resolution issue. Here are the steps:

Update the ACPX_PINNED_VERSION to match the bundled acpx version (0.3.0):
- Set plugins.entries.acpx.config.expectedVersion to "0.3.0" in the gateway configuration.
Resolve the Windows .cmd wrapper issue:
- Set plugins.entries.acpx.config.strictWindowsCmdWrapper to false in the gateway configuration.
- Ensure the acpx.cmd wrapper is correctly resolved by setting plugins.entries.acpx.config.command to the direct path of the acpx executable (e.g., ...\acpx\dist\cli.js).

Example configuration changes:

// gateway configuration
plugins: {
  entries: {
    acpx: {
      config: {
        expectedVersion: "0.3.0",
        strictWindowsCmdWrapper: false,
        command: "...\acpx\dist\cli.js"
      }
    }
  }
}

Alternatively, you can try setting expectedVersion to "any" to bypass version checks:

// gateway configuration
plugins: {
  entries: {
    acpx: {
      config: {
        expectedVersion: "any"
      }
    }
  }
}

Verification

After applying the configuration changes, restart the gateway and verify that the ACP backend is available. Check the gateway logs for any errors related to the acpx plugin.

Extra Tips

Ensure that the acpx version is consistent across all environments to avoid version mismatch issues.
If you encounter further issues, try resetting the openclaw node modules directory by running npm install -g openclaw@latest --force and restarting the gateway.

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?

FAQ

Expected behavior

Either the bundled acpx version matches ACPX_PINNED_VERSION, or expectedVersion: "any" should fully bypass all version/binary checks and allow the plugin to initialize normally.

#api #ssr #installation #tensor shape #autograd error #batch processing #GPU compatibility #latency issue #model loading #dependency error

Still need to ship something?

×6

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

Data

Security

Network

Code

UI/UX

Text

System

Multimedia

Protocol

API

Engineering

openclaw - ✅(Solved) Fix [Bug] 2026.3.13 Windows: ACP runtime unavailable after update — acpx 0.3.0 vs pinned 0.1.16, expectedVersion:any workaround not effective [1 pull requests, 2 comments, 3 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fix / Workaround

Workarounds attempted (none resolved the issue)

PR fix notes

PR #51867: fix(acpx): align pinned version with bundled 0.3.0 and wrapper fallback

Description (problem / solution / changelog)

Summary

Changed files

Code Example

Summary

Environment

Errors in gateway log

Steps to reproduce

Workarounds attempted (none resolved the issue)

Relationship to #43997

Expected behavior

extent analysis

Fix Plan

Verification

Extra Tips

FAQ

Expected behavior

Still need to ship something?

TRENDING

openclaw - ✅(Solved) Fix [Bug] 2026.3.13 Windows: ACP runtime unavailable after update — acpx 0.3.0 vs pinned 0.1.16, expectedVersion:any workaround not effective [1 pull requests, 2 comments, 3 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fix / Workaround

Workarounds attempted (none resolved the issue)

PR fix notes

PR #51867: fix(acpx): align pinned version with bundled 0.3.0 and wrapper fallback

Description (problem / solution / changelog)

Summary

Changed files

Code Example

Summary

Environment

Errors in gateway log

Steps to reproduce

Workarounds attempted (none resolved the issue)

Relationship to #43997

Expected behavior

extent analysis

Fix Plan

Verification

Extra Tips

FAQ

Expected behavior

Still need to ship something?

RELATED_DISCOVERY

TRENDING