OpenClaw /acp spawn claude fails with ACP_TURN_FAILED while direct acpx claude succeeds

[notfound-999]

OpenClaw /acp spawn claude fails with ACP_TURN_FAILED while direct acpx claude succeeds

Summary

Claude CLI and direct acpx claude both work, but OpenClaw /acp spawn claude fails with ACP_TURN_FAILED / UNAVAILABLE / Internal error.

What works

• Gateway probe/status stable
• Codex standard ACP works
• Claude CLI no-write smoke works
• direct acpx Claude no-write smoke works

What fails

• OpenClaw /acp spawn claude --mode oneshot ...
• Error: ACP_TURN_FAILED, surfaced as UNAVAILABLE / AcpRuntimeError: Internal error
• No timeout
• No auth error
• No module/dependency error visible in redacted logs

Environment

• OpenClaw: 2026.5.5
• @openclaw/acpx: 2026.5.4
• acpx: 0.6.1 plugin-local
• @agentclientprotocol/claude-agent-acp: 0.32.0
• @anthropic-ai/claude-agent-sdk: 0.2.126
• @agentclientprotocol/sdk: 0.21.0
• Claude Code: 2.1.92
• Node: v25.9.0
• macOS: Darwin 25.3.0 arm64

Repro steps

1. Run Claude CLI no-write smoke.
2. Run direct acpx Claude no-write smoke.
3. Run OpenClaw /acp spawn claude no-write smoke.
4. Observe ACP_TURN_FAILED / Internal error.

Expected

OpenClaw /acp spawn claude should return:

CLAUDE_OPENCLAW_ACP_READY

Actual

OpenClaw path fails with:

ACP_TURN_FAILED / UNAVAILABLE / Internal error

Impact

• Codex standard ACP is usable
• Claude standard ACP is unusable
• Automatic Codex + Claude two-agent ACP flow is blocked
• Temporary workaround: Codex standard ACP + Claude CLI/manual review

Notes

• This does not appear to be Claude CLI auth, Gateway timeout, or direct adapter failure.
• Direct acpx Claude succeeds from the same host.
• Gateway is stable after disabling magi-discord-guard.
• Secrets, auth files, and raw full logs are not included.