Bug type

Behavior bug (incorrect output/state without crash)

Summary

When starting the gateway, the gateway signals that it is running, but openclaw still acts like the gateway is disconnected.

I normally run openclaw though a wrapper, but ran a test that used:

• separate OPENCLAW_HOME
• separate config
• separate port
• foreground gateway run
• explicit --url / --token

*gateway health still failed with websocket 1006, even while the gateway reported itself as running.

Figured it was worth noting on here just in case anyone else was havinng this issue.

Steps to reproduce

Steps (checked with codex):

Run pnpm openclaw gateway install
Run pnpm openclaw gateway start
Run pnpm openclaw gateway status
Run pnpm openclaw gateway health --timeout 3500
See that gateway status can report the gateway as running/listening while gateway health still fails with WebSocket 1006

Isolated repo test:
Create a separate OpenClaw config/home on a different port
Run pnpm openclaw gateway run --port 18889 --bind loopback --auth token --token --allow-unconfigured
In another shell, run pnpm openclaw gateway health --timeout 3500 --url ws://127.0.0.1:18889 --token
See gateway health fail with WebSocket 1006 even though the gateway is running/listening

Expected behavior

Gateway health should succeed whenever the gateway is already running and listening.

Actual behavior

gateway showed as running, but gateway health still failed and acted like the gateway was disconnected, returning WebSocket 1006.

OpenClaw version

2026.3.9

Operating system

macOS 15.7.4

Install method

pnpm dev / local source checkout

Model

openai-codex/gpt-5.4

Provider / routing chain

openclaw gateway -> codex/gpt-5.4

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