openclaw - 💡(How to fix) Fix WebChat: WebSocket drops every 1-5 minutes on Safari, loses messages and tool-call events on reconnect [1 comments, 1 participants]

The Control UI webchat WebSocket connection drops frequently (every 1-5 minutes) when opened in Safari on macOS. After reconnect, messages and events (tool call displays, error messages) that occurred during the disconnect are lost — the user sees a stale view and must manually refresh. 3. Error messages only go to Telegram — e.g., JSON parse errors surface on Telegram but never appear in webchat 3. Tool call events and error messages should be persisted and delivered on reconnect, not silently dropped

TL;DR

Implementing a keepalive mechanism, such as sending periodic pings over the WebSocket connection, may help prevent Safari from throttling the connection.

Guidance

• Investigate the feasibility of implementing a keepalive ping mechanism in the webchat client to maintain an active connection and prevent Safari's aggressive throttling.
• Verify if the WebSocket gateway supports and can handle keepalive pings without issues.
• Consider modifying the webchat client to request missed messages and events upon reconnect, ensuring a seamless user experience.
• Review the WebSocket connection settings and parameters to ensure they are optimized for the specific use case and environment.

Example

A simple keepalive ping mechanism could involve sending a small message over the WebSocket connection at regular intervals, e.g., every 10-15 seconds, to keep the connection active.

Notes

The effectiveness of the keepalive mechanism may vary depending on Safari's specific throttling behavior and the WebSocket gateway's implementation. Testing and verification are necessary to ensure the chosen solution works as expected.

Recommendation

Apply a workaround by implementing a keepalive ping mechanism to prevent Safari from throttling the WebSocket connection, as upgrading to a fixed version is not mentioned as an option in the issue description.