Environment

• OpenClaw: 2026.2.26 (bc50708)
• OS: Windows 11 (10.0.26200) x64
• Node: 24.13.0
• acpx: 0.1.13 (installed globally and plugin-local)
• Gateway runs as Windows Scheduled Task

Problem

The acpx plugin fails to verify its local binary when running under a Windows Scheduled Task, even though the binary exists and works fine from an interactive shell.

Log output

\
[plugins] acpx runtime backend registered (command: ...extensions\acpx\node_modules.bin\acpx.cmd, pinned: 0.1.13)
[plugins] acpx local binary unavailable or mismatched (The system cannot find the path specified.); running plugin-local install
[plugins] acpx runtime setup failed: npm is required to install plugin-local acpx but was not found on PATH
\\

Steps to reproduce

1. Install OpenClaw on Windows with gateway running as Scheduled Task
2. Enable \�cp.enabled=true, \�cp.dispatch.enabled=true, \�cp.backend=acpx\
3. 
   pm install -g acpx\ and also
   pm install\ inside \extensions/acpx/\
4. Restart gateway
5. The plugin registers the binary path but then fails verification

Analysis

• The \gateway.cmd\ sets PATH correctly (includes \C:\Program Files\nodejs\ where npm.cmd lives)
• The \�cpx.cmd\ shim in
  ode_modules/.bin/\ uses %dp0%\ relative paths which may not resolve correctly under the Scheduled Task runner context
• The plugin then falls back to
  pm install\ but can't find npm (even though it's on PATH) - likely because it looks for bare
  pm\ without .cmd\ extension
• Replacing the .bin/acpx.cmd\ with absolute paths didn't help because the verification step runs before execution

Expected behavior

acpx plugin should work when running as a Windows Scheduled Task service.

Workaround attempted

• Manually installed acpx globally and plugin-local
• Replaced acpx.cmd shim with absolute paths
• Regenerated gateway.cmd with \openclaw gateway install --force\
• None resolved the issue