openclaw - 💡(How to fix) Fix ACP runtime sessions fail with 'acpx exited with code 1' — sessions_spawn runtime:"acp" broken in 2026.4.2 [1 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#60585Fetched 2026-04-08 02:49:24
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
1
Participants
Timeline (top)
commented ×1subscribed ×1

Error Message

[plugins] acpx ensureSession repairing dead named session: session=agent:claude:acp:... cwd=/Users/andreas/.openclaw/workspace status=dead summary=queue owner unavailable
[plugins] acpx ensureSession dead-session resume repair failed; retrying with fresh session owner: session=agent:claude:acp:... cwd=... resumeSessionId=... error=-32002: Resource not found: ...
[plugins] acpx ensureSession dead-session resume repair failed; retrying with fresh session owner: session=agent:claude:acp:... cwd=... resumeSessionId=... error=-32002: Resource not found: ...
[ws] res ✗ agent errorCode=UNAVAILABLE errorMessage=AcpRuntimeError: acpx exited with code 1

Fix Action

Fix / Workaround

Cannot use sessions_spawn runtime:"acp" for background Codex tasks. Workaround is to use direct exec calls to acpx codex binary, but this bypasses OpenClaw's session management.

Code Example

Background task failed: ACP background task (run XXX). acpx exited with code 1

---

[plugins] acpx ensureSession repairing dead named session: session=agent:claude:acp:... cwd=/Users/andreas/.openclaw/workspace status=dead summary=queue owner unavailable
[plugins] acpx ensureSession dead-session resume repair failed; retrying with fresh session owner: session=agent:claude:acp:... cwd=... resumeSessionId=... error=-32002: Resource not found: ...
[plugins] acpx ensureSession dead-session resume repair failed; retrying with fresh session owner: session=agent:claude:acp:... cwd=... resumeSessionId=... error=-32002: Resource not found: ...
[ws] res ✗ agent errorCode=UNAVAILABLE errorMessage=AcpRuntimeError: acpx exited with code 1

---

"plugins": {
  "entries": {
    "acpx": {
      "enabled": true,
      "config": {
        "permissionMode": "approve-all",
        "nonInteractivePermissions": "fail"
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Bug Description

sessions_spawn runtime:"acp" fails with "acpx exited with code 1" in OpenClaw 2026.4.2. This appears after the Task Flow system changes in the 2026.4.2 release.

Steps to Reproduce

  1. Have Codex CLI installed and authenticated (codex auth status shows OK)
  2. Attempt sessions_spawn runtime:"acp" with any task
  3. ACP backend fails immediately with "acpx exited with code 1"

Expected Behavior

sessions_spawn runtime:"acp" should create a live ACP session and execute the task.

Actual Behavior

Background task failed: ACP background task (run XXX). acpx exited with code 1

The error occurs during session creation/repair, not during task execution.

Environment

  • OpenClaw: 2026.4.2 (d74a122)
  • macOS: Darwin 25.3.0 (arm64)
  • Node: v22.22.0
  • acpx: 0.4.0 (plugin-local, correctly installed at /opt/homebrew/lib/node_modules/openclaw/dist/extensions/acpx/node_modules/.bin/acpx)
  • Codex CLI: v0.112.0, authenticated via ChatGPT Plus

Logs

[plugins] acpx ensureSession repairing dead named session: session=agent:claude:acp:... cwd=/Users/andreas/.openclaw/workspace status=dead summary=queue owner unavailable
[plugins] acpx ensureSession dead-session resume repair failed; retrying with fresh session owner: session=agent:claude:acp:... cwd=... resumeSessionId=... error=-32002: Resource not found: ...
[plugins] acpx ensureSession dead-session resume repair failed; retrying with fresh session owner: session=agent:claude:acp:... cwd=... resumeSessionId=... error=-32002: Resource not found: ...
[ws] res ✗ agent errorCode=UNAVAILABLE errorMessage=AcpRuntimeError: acpx exited with code 1

Direct acpx verification

The acpx binary works correctly when called directly:

  • acpx codex sessions list → works
  • acpx codex sessions new → creates session successfully
  • acpx codex -s <session> <prompt> → executes prompts correctly

The issue is specifically in OpenClaw's ACP runtime integration, not in acpx itself.

Config

"plugins": {
  "entries": {
    "acpx": {
      "enabled": true,
      "config": {
        "permissionMode": "approve-all",
        "nonInteractivePermissions": "fail"
      }
    }
  }
}

Possible Related Changes (2026.4.2)

From CHANGELOG:

  • "Tasks/Task Flow: restore the core Task Flow substrate with managed-vs-mirrored sync modes, durable flow state/revision tracking, and openclaw flows inspection/recovery primitives so background orchestration can persist..."
  • "Plugins/Task Flow: add a bound api.runtime.taskFlow seam so plugins and trusted authoring layers can create and drive managed Task Flows from host-resolved OpenClaw context..."

This suggests significant changes to the Task Flow system that the ACP runtime depends on.

Impact

Cannot use sessions_spawn runtime:"acp" for background Codex tasks. Workaround is to use direct exec calls to acpx codex binary, but this bypasses OpenClaw's session management.

extent analysis

TL;DR

The issue with sessions_spawn runtime:"acp" failing in OpenClaw 2026.4.2 is likely due to compatibility problems with the updated Task Flow system, and a workaround involves using direct acpx commands.

Guidance

  • Verify that the acpx version is compatible with the updated Task Flow system in OpenClaw 2026.4.2.
  • Check the OpenClaw configuration to ensure that the ACP runtime integration is correctly set up.
  • Consider using the direct acpx commands as a temporary workaround until the compatibility issue is resolved.
  • Review the CHANGELOG for OpenClaw 2026.4.2 to understand the changes made to the Task Flow system and how they may affect the ACP runtime integration.

Example

No code example is provided as the issue is related to configuration and compatibility rather than code.

Notes

The issue seems to be specific to the OpenClaw's ACP runtime integration and not with the acpx binary itself, as verified by direct acpx commands working correctly.

Recommendation

Apply the workaround of using direct acpx commands until the compatibility issue with the updated Task Flow system is resolved, as this allows for continued use of background Codex tasks while bypassing the problematic OpenClaw session management.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING