Description

The gateway health check occasionally fails with a WebSocket 1006 error (abnormal closure without close frame).

Error message

Health check failed: gateway closed (1006 abnormal closure (no close frame)): no close reason
  Gateway target: ws://127.0.0.1:18789
  Source: local loopback
  Bind: loopback

Environment

• OS: macOS 26.2 (arm64)
• Node: v22.22.0
• OpenClaw: 2026.2.1 (stable)
• Gateway: LaunchAgent, loopback bind

Observed behavior

• Health check fails intermittently
• Gateway appears to close the WebSocket connection without sending a proper close frame
• After the failure, the gateway recovers and runs normally
• Observed twice within ~1 minute (11:03:23 and 11:04:19)

Expected behavior

Gateway should either:

1. Not drop the connection unexpectedly
2. Send a proper close frame if restarting/shutting down

Additional context

The gateway was running as a LaunchAgent service. No manual restart was triggered. The process recovered on its own (or was restarted by launchd).

Possibly related to memory pressure, service restart, or an internal error that caused the gateway to terminate abruptly.