acpx extension has inconsistent pinned version: package.json depends on 0.3.0 but runtime doctor/config still enforces 0.1.16

[chestnut111]

Summary

The OpenClaw extensions/acpx package appears to have an internal version mismatch.

In my installation:

• extensions/acpx/package.json declares:
• "acpx": "0.3.0"
• but runtime doctor / config still expects:
• 0.1.16

This leads to confusing and potentially broken behavior around ACP sessions.

Environment

• OpenClaw: 2026.3.13 (61d171a)
• Installed via: nvm / node v24.13.1
• OS: macOS
• Extension path:
• /Users/lixin/.nvm/versions/node/v24.13.1/lib/node_modules/openclaw/extensions/acpx

Evidence

1) package.json declares acpx 0.3.0

extensions/acpx/package.json:
json
{
"name": "@openclaw/acpx",
"version": "2026.3.13",
"description": "OpenClaw ACP runtime backend via acpx",
"type": "module",
"dependencies": {
"acpx": "0.3.0"
},
"openclaw": {
"extensions": ["./index.ts"]
}
}

2) runtime config still pins 0.1.16

Found in source:
ts
export const ACPX_PINNED_VERSION = "0.1.16";
From:

• extensions/acpx/src/config.ts
• extensions/acpx/openclaw.plugin.json also references exact enforced version behavior

3) ACP doctor reports expected 0.1.16

Example output:
txt
ACP doctor:

configuredBackend: acpx
activeRuntimeSessions: 0
runtimeIdleTtlMs: 0
evictedIdleRuntimes: 0
activeTurns: 0
queueDepth: 0
turnLatencyMs: avg=0, max=0
turnCounts: completed=0, failed=0
errorCodes: (none)
registeredBackend: acpx
runtimeDoctor: ok (acpx command available (/Users/lixin/.nvm/versions/node/v24.13.1/lib/node_modules/openclaw/extensions/acpx/node_modules/.bin/acpx, version 0.1.16, expected 0.1.16))
healthy: yes
capabilities: session/set_config_option, session/set_mode, session/status

User-visible symptoms

I hit repeated / stuck ACP behavior in Discord:

• repeated welcome / ready messages from the Claude ACP session
• after manually closing the underlying acpx session, Discord kept receiving repeated:
• ACP error (ACP_TURN_FAILED): acpx exited with code 4
• /acp cancel did not resolve it
• openclaw gateway restart stopped the repeated error output

I cannot prove the version mismatch is the sole cause, but it is highly suspicious and definitely confusing.

Reproduction notes

1. Inspect extensions/acpx/package.json

• dependency says acpx: 0.3.0

2. Inspect extensions/acpx/src/config.ts

• runtime pinned version says 0.1.16

3. Run ACP doctor

• doctor reports expected 0.1.16

4. Try to align local install to 0.3.0

• doctor/runtime still expects 0.1.16

Expected behavior

The extension should have a single source of truth for the acpx version:

• either package.json and runtime pin both use 0.3.0
• or both use 0.1.16

ACP doctor, installer/repair logic, and runtime execution should all agree on the same version.

Actual behavior

Different parts of the extension disagree about the expected acpx version:

• package dependency says 0.3.0
• runtime/config/doctor says 0.1.16

This makes troubleshooting difficult and may contribute to unstable ACP runtime behavior.

Suggested fix

Please make the extension internally consistent:

• update src/config.ts pinned version to match package.json, or
• revert package.json dependency to match the actual runtime pin

Also worth checking:

• any compiled output / bundled config that still embeds 0.1.16
• doctor/install-repair paths
• gateway runtime behavior when the underlying acpx session disappears mid-turn