openclaw - 💡(How to fix) Fix [Bug] Feishu WebSocket closes after each message in v2026.3.13 [2 comments, 3 participants]

Fix Plan

To resolve the issue of the Feishu WebSocket connection closing after each message in OpenClaw v2026.3.13, we need to modify the WebSocket handling logic.

1. Update WebSocket Connection Handling:
   • Ensure that the WebSocket connection remains open after receiving a message.
   • Modify the onMessage event handler to not close the connection.

Example code snippet (assuming a Node.js environment):

// Assuming 'ws' is your WebSocket object
ws.on('message', (message) => {
  // Process the message
  console.log(`Received message: ${message}`);
  
  // Do not close the connection here
  // ws.close(); // Comment out or remove this line if present
});

1. Implement Reconnection Logic:
   • If the connection is closed unexpectedly, implement a reconnection mechanism.
   • Use ws.on('close', ...) and ws.on('error', ...) to detect closure and errors, and attempt to reconnect.

Example code snippet:

let reconnectTimeout = 1000; // 1 second

ws.on('close', () => {
  console.log('WebSocket connection closed. Reconnecting...');
  setTimeout(() => {
    // Reconnect logic here
    // For example, call a function that establishes a new WebSocket connection
    establishWebSocketConnection();
  }, reconnectTimeout);
});

ws.on('error', (error) => {
  console.error('WebSocket error:', error);
  // Optionally, attempt to reconnect here as well
});

1. Review OpenClaw Configuration:
   • Check the OpenClaw configuration for any settings related to WebSocket connections that might be causing the issue.
   • Adjust these settings as necessary to ensure continuous message reception.

Verification

To verify that the fix worked:

• Send multiple messages to the bot in Feishu.
• Check the logs for any "ws client closed manually (force)" messages.
• Ensure that all messages are received correctly without needing to restart the gateway.

Extra Tips

• Regularly review updates to OpenClaw and its dependencies for any changes that might affect WebSocket connection handling.
• Consider implementing additional logging to monitor WebSocket connection states and message reception for easier debugging.