openclaw - 💡(How to fix) Fix WebChat: frontend stuck in streaming state after backend completes response

Bug Description

In the WebChat UI, after the backend has fully completed generating a response, the frontend still shows the "streaming/generating" indicator. The complete content only becomes visible after manually refreshing the browser page.

Environment

• OpenClaw version: 2026.5.20
• macOS 15.6.1 arm64
• Node.js 22.22.1
• Channel: webchat
• Browser: (not confirmed, likely Chrome/Chromium)
• Primary model: zai/glm-5.1

Steps to Reproduce

1. Use WebChat to send a message
2. Wait for the backend to complete the response (verified via logs/backend shows completion)
3. Observe the frontend still shows streaming/loading indicator
4. The UI remains stuck until page refresh

Expected Behavior

Frontend should update to show the completed response immediately when the backend finishes streaming, without requiring a manual page refresh.

Actual Behavior

Frontend remains in streaming state. Refreshing the page reveals the complete response content (no truncation).

Additional Context

• This appears to be a WebSocket state synchronization issue — the completion signal may not be reaching the frontend
• Possible causes: SSE stream missing [DONE] marker, WebSocket reconnection losing completion events, or context compaction interfering with completion signal delivery
• The response content is always complete after refresh (not truncated), suggesting the data is persisted correctly but the frontend state is not updated

Frequency

Intermittent but recurring. Occurs frequently enough to be disruptive to normal usage.