Description

ACP runtime (acpx plugin) fails to initialize on Windows with:

\
acpx local binary unavailable or mismatched ((0 , _pluginSdk.resolveWindowsSpawnProgramCandidate) is not a function); running plugin-local install
acpx runtime setup failed: (0 , _pluginSdk.resolveWindowsSpawnProgramCandidate) is not a function
\\

The acpx extension (\�xtensions/acpx/src/runtime-internals/process.ts:11) imports
esolveWindowsSpawnProgramCandidate\ from \openclaw/plugin-sdk, but the core plugin SDK (\dist/plugin-sdk/index.js) does not export this function. The SDK has 299 exports — none include
esolveWindowsSpawnProgramCandidate.

Impact

• ACP is completely broken on Windows — both one-shot and persistent sessions fail
• \sessions_spawn\ with
  untime: 'acp'\ returns: \ACP runtime backend is currently unavailable\
• The acpx CLI binary itself works fine (\�cpx --version\ returns 0.1.15)

Reproduction

1. Install OpenClaw v2026.3.2 on Windows
2. Enable acpx plugin: \plugins.entries.acpx.enabled = true\
3. Try /acp spawn codex\ or \sessions_spawn\ with
   untime: 'acp'\
4. Error: backend unavailable

Environment

• OS: Windows 11 (10.0.26200)
• Node: v22.13.1
• OpenClaw: v2026.3.2 (also reproduced on v2026.3.1)
• acpx: 0.1.15 (plugin-local)

Config workarounds attempted (all failed)

• Setting \plugins.entries.acpx.config.command\ to explicit binary path
• Setting \plugins.entries.acpx.config.expectedVersion\ to \�ny\
• Updating acpx extension dependencies (
  pm install\ inside extensions/acpx)

None bypass the issue because
esolveWindowsSpawnProgramCandidate\ is called unconditionally in the runtime setup path.

Fix suggestion

Either:

1. Export
   esolveWindowsSpawnProgramCandidate\ from the core plugin SDK
2. Or add a graceful fallback in the acpx extension when the function is unavailable