## Summary
Control UI fails to render new agent messages after a successful chat.history WebSocket response.
Steps to reproduce
Open the OpenClaw Gateway Control UI and navigate to a chat session.
Have a conversation with the agent.
The agent sends a reply. This can be a simple text message or a message that follows a tool execution.
Expected behavior
The agent's new message should appear automatically in the chat window, appending to the conversation history without requiring a page refresh.
Actual behavior
The agent's final message does not render in the UI. The chat window appears stuck, not showing the latest reply.
However, the browser's developer console shows that the data is being received successfully. A log line similar to this one appears each time a message fails to render:
[ws] ⇄ res ✓ chat.history
This indicates the browser receives the updated history but a bug in the UI's rendering logic prevents it from being displayed. A manual hard refresh of the page (Ctrl+Shift+R) forces the UI to reload and correctly displays the missing message.
Environment
OpenClaw version: 2026.2.2-3
OS: Windows
Install method (pnpm/npx/docker/etc): (Per favore, compila tu questo campo con il metodo che hai usato per installare OpenClaw)
Logs or screenshots
The key log line from the browser console is:
00:01:28 [ws] ⇄ res ✓ chat.history 54ms conn=07128aa2…6eba id=1361a055…7fdc
Steps to reproduce
Open the OpenClaw Gateway Control UI and navigate to a chat session.
Have a conversation with the agent.
The agent sends a reply. This can be a simple text message or a message that follows a tool execution.
Expected behavior
The agent's new message should appear automatically in the chat window, appending to the conversation history without requiring a page refresh.
Actual behavior
The agent's final message does not render in the UI. The chat window appears stuck, not showing the latest reply.
However, the browser's developer console shows that the data is being received successfully. A log line similar to this one appears each time a message fails to render:
[ws] ⇄ res ✓ chat.history
This indicates the browser receives the updated history but a bug in the UI's rendering logic prevents it from being displayed. A manual hard refresh of the page (Ctrl+Shift+R) forces the UI to reload and correctly displays the missing message.
Environment
OpenClaw version: 2026.2.2-3
OS: Windows
Install method (pnpm/npx/docker/etc): (Per favore, compila tu questo campo con il metodo che hai usato per installare OpenClaw)
Logs or screenshots
The key log line from the browser console is:
00:01:28 [ws] ⇄ res ✓ chat.history 54ms conn=07128aa2…6eba id=1361a055…7fdc