Summary

Clicking Refresh chat data in the Control UI while an agent turn is still active can stall the live run and leave the web UI effectively wedged. In the reported case, the gateway also appeared to lock up badly enough that the page stopped working until recovery/restart.

Steps to reproduce

1. Open the OpenClaw Control UI and go to the chat tab.
2. Start a chat turn that produces a live agent response / active run.
3. While the agent turn is still in progress, click the Refresh chat data button in the chat controls.
4. Watch the active run and the page state.

Expected behavior

Refreshing chat data during an active run should either:

• be disabled / ignored while the run is in progress, or
• safely refresh visible chat state without interfering with the active run or gateway responsiveness.

Actual behavior

Refreshing during the active turn appears to trigger a stall:

• the active run stops making progress
• the chat UI can get stuck
• the page may stop working normally afterward
• the gateway may need manual recovery / restart

Impact

This is a bad-footgun in the Control UI because a single button press during a live turn can wedge the current conversation and potentially the gateway session behind it.

Environment

• OpenClaw version: 2026.4.10
• Commit: 163d555f70
• Platform: Darwin arm64
• Surface: Control UI / web chat
• Local checkout: openclaw/openclaw

Notes

The button label in the UI is Refresh chat data.

This report is specifically about pressing it during an active agent turn, not while the chat is idle.