Skip to content

[Bug]: v2026.3.31 breaks exec on local loopback setups #59045

@clumsyzombie

Description

@clumsyzombie

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading to v2026.3.31, all exec calls fail with:
"gateway closed (1008): pairing required"

This affects even basic commands like openclaw --version. The exec
tool cannot authenticate to the gateway on local loopback (ws://127.0.0.1:18789).

Gateway token auth IS configured (gateway.auth.mode: "token"), but
the exec tool apparently cannot use it — every exec call registers
and fails immediately.

Expected behavior

exec should work on local loopback with token auth (worked in v2026.3.28)

Version

  • OpenClaw: 2026.3.31
  • Node: v24.14.1
  • OS: WSL2 (linux 6.6.87.2-microsoft-standard-WSL2)
  • Gateway: local loopback, auth token configured

Workaround

Downgrade to v2026.3.28

Steps to reproduce

  1. Have gateway running with auth.token configured + bind=loopback
  2. Upgrade to v2026.3.31
  3. Attempt any exec call (CLI or agent tool)

Expected behavior

exec should work on local loopback with token auth (worked in v2026.3.28)

Actual behavior

Workaround
Downgrade to v2026.3.28

OpenClaw version

2026.3.31

Operating system

WSL2 (linux 6.6.87.2-microsoft-standard-WSL2)

Install method

No response

Model

minimax2.7

Provider / routing chain

local loopback, auth token configured

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingregressionBehavior that previously worked and now fails

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions