openclaw - 💡(How to fix) Fix WebChat WebSocket drops (1006) during long model turns — missing keepalive pings [1 participants]

TL;DR

Implementing a WebSocket ping/keepalive mechanism is likely necessary to prevent the connection from dropping with code 1006 during long model responses.

Guidance

• Investigate the OpenClaw 2026.4.2 documentation for any hidden or undocumented configuration options that may allow setting a keepalive or ping interval for WebSocket connections.
• Consider modifying the gateway to send periodic WebSocket ping frames during long model turns to keep the connection alive, potentially using a custom implementation if no built-in option is available.
• Review the WebSocket connection handling in the Control UI webchat to ensure it properly handles ping frames and responds accordingly to prevent silent drops.
• Test the reproduction steps with different model configurations to confirm the issue is specific to long response times and not related to other factors.

Example

No specific code example can be provided without more information on the gateway and Control UI webchat implementation details.

Notes

The lack of explicit errors or timeouts in the gateway logs suggests the issue may be related to the WebSocket connection handling or the keepalive mechanism. The consistent repetition of the disconnection pattern points towards a specific trigger, in this case, long model responses.

Recommendation

Apply a workaround by implementing a custom WebSocket ping/keepalive mechanism, as there is no clear indication that upgrading to a different version of OpenClaw would resolve the issue, and the problem seems to be related to the specific configuration and usage of the gateway and Control UI webchat.