Bug type

Regression (worked before, now fails)

Summary

Summary

After upgrading OpenClaw from 2026.3.8 to 2026.3.13, several CLI/gateway handshake paths regressed in my environment.

The regression was confirmed by rollback:

• 2026.3.8: works
• 2026.3.13: broken
• rollback to 2026.3.8: works again

Environment

• OpenClaw versions tested:
• working: 2026.3.8
• broken: 2026.3.13
• OS: Linux
• Gateway mode: local
• Bind: loopback
• Tailscale serve enabled
• ACP enabled
• Main workflow depends on ACP bridge + normal CLI/gateway device paths

What broke on 2026.3.13

These worked before the upgrade and failed after:

• openclaw devices list timed out before hello
• openclaw gateway probe timed out
• pairing/probe-style paths failed
• ACP path was broken end-to-end during the regression window

There also appeared to be CLI auth/identity handling issues during loopback CLI calls, where calls seemed to downgrade into a missing scope/state path (operator.read was involved during investigation).

What still worked / partial observations

• The gateway daemon itself stayed healthy
• The issue looked narrower than a total gateway failure
• openclaw status was later made to work during investigation, but other probe/pair/device paths still failed on 2026.3.13

Rollback result

After rolling back to 2026.3.8 and refreshing the systemd gateway service:

Working again:

• openclaw status
• openclaw devices list
• openclaw acp -v
• ACP end-to-end workflow

Verified ACP recovery with real workflow:

• one-shot ACP test succeeded
• persistent ACP session test succeeded
• turn 1: “Remember the word ORBIT” -> stored
• turn 2 on same session -> “ORBIT”
  This strongly suggests a regression in 2026.3.13 rather than an environment-only issue.

Additional note

openclaw gateway probe still times out on 2026.3.8 as well, so that specific probe timeout may be a separate older issue.

Expected behavior

Upgrading from 2026.3.8 to 2026.3.13 should not break:

• ACP bridge/session routing
• normal CLI device/pair/probe handshake paths
• loopback CLI identity/scope attachment

Actual behavior

2026.3.13 introduced handshake/path regressions severe enough that I had to roll back to 2026.3.8.

Steps to reproduce

Upgrading OpenClaw from 2026.3.8 to 2026.3.13

Expected behavior

Normal clean upgrade. ACP functioning

Actual behavior

No ACP

OpenClaw version

2026.3.13

Operating system

Linux

Install method

npm

Model

openai-codex/gpt-5.4

Provider / routing chain

openclaw

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response