openclaw - 💡(How to fix) Fix [Bug]：TUI enters infinite reconnect loop on WebSocket close (code 1006) [1 comments, 2 participants]

TUI repeatedly reconnects on WebSocket close (code 1006) without stopping or showing the underlying error. TUI should stop retrying after connection failure or show a clear error message. Consequence: Terminal flooded, underlying error not visible

TL;DR

The TUI should be modified to handle WebSocket close events with code 1006 by stopping retry attempts or displaying the underlying error message.

Guidance

• Investigate the WebSocket connection handling in the TUI code to identify why it's not stopping or showing the error after a close event with code 1006.
• Consider implementing a retry limit or a backoff strategy to prevent indefinite reconnect attempts.
• Review the error handling mechanism to ensure that the underlying error is properly propagated and displayed to the user.
• Check if there are any existing configuration options or environment variables that can be used to control the TUI's reconnect behavior.

Example

No code example is provided due to the lack of specific code context in the issue.

Notes

The issue seems to be specific to the TUI's handling of WebSocket close events, and the solution may involve modifying the TUI code to properly handle these events.

Recommendation

Apply workaround: Modify the TUI code to handle WebSocket close events with code 1006 by stopping retry attempts or displaying the underlying error message, as this is a high-severity issue that makes the CLI unusable.