Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Control UI: Thinking icon disappears after ~1 minute and conversation goes blank (webchat channel) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73246•Fetched 2026-04-29 06:21:52
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
keersyskeersys
Participants
keersyskeersysopenclaw-barnacle[bot]openclaw-barnacle[bot]
Timeline (top)
labeled ×2closed ×1commented ×1

Root Cause

Possible Root Cause

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Bug Description

In QClaw's openclaw-control-ui (desktop client), when using the webchat channel, the thinking icon appears after sending a message, but disappears after approximately 1 minute without any response being rendered. The conversation area goes completely blank. The issue is reproducible in the QClaw desktop client but NOT in the localhost:28789 web browser webchat.

Environment

  • QClaw version: 2026.4.5
  • Channel: webchat (openclaw-control-ui desktop client)
  • Operating system: Windows 11
  • Model: qclaw/modelroute (reasoning=false)

Steps to Reproduce

  1. Open the QClaw desktop client (openclaw-control-ui)
  2. Send a message that triggers a longer AI response
  3. Observe the thinking icon appears
  4. After approximately 1 minute, the thinking icon disappears
  5. The conversation area is now completely blank — no thinking content, no AI response

Expected Behavior

The thinking icon should remain visible until the AI produces a response, and the response should be rendered in the conversation area.

Additional Observations

  • This issue does NOT occur in the web browser version (localhost:28789 with token auth)
  • The webchat via browser works correctly even with the same QClaw Gateway
  • The issue appears to be specific to the openclaw-control-ui desktop client
  • Gateway config is identical for both clients (port 28789, same token)

Possible Root Cause

The issue is suspected to be in the Electron rendering layer of openclaw-control-ui, possibly related to:

  1. WebSocket connection handling for long-running requests
  2. UI state reset when processing takes longer than a threshold
  3. Stream/event handling in the control UI client

Tags

  • client (openclaw-control-ui)
  • webchat channel
  • rendering

Steps to reproduce

NOT_ENOUGH_INFO

Expected behavior

NOT_ENOUGH_INFO

Actual behavior

NOT_ENOUGH_INFO

OpenClaw version

v2026.4.5

Operating system

Windows11

Install method

No response

Model

qclaw/modelroute

Provider / routing chain

qclaw/modelroute

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can likely be fixed by adjusting the WebSocket connection handling or UI state management in the openclaw-control-ui desktop client to prevent the conversation area from going blank after a minute.

Guidance

  • Investigate the Electron rendering layer of openclaw-control-ui for potential issues with WebSocket connection handling for long-running requests.
  • Check the UI state reset logic to ensure it doesn't interfere with the rendering of the thinking icon and AI response after a certain threshold.
  • Compare the WebSocket connection and event handling implementations between the openclaw-control-ui desktop client and the web browser version to identify potential differences.
  • Verify that the issue is not related to the qclaw/modelroute model or the QClaw Gateway configuration, as the web browser version works correctly with the same setup.

Example

No code snippet can be provided without more specific information about the implementation details of the openclaw-control-ui desktop client.

Notes

The root cause of the issue is still speculative, and further investigation is needed to determine the exact cause. The fact that the issue only occurs in the desktop client and not in the web browser version suggests that the problem might be related to the Electron rendering layer or the WebSocket connection handling in the desktop client.

Recommendation

Apply a workaround by adjusting the WebSocket connection handling or UI state management in the openclaw-control-ui desktop client, as the issue seems to be specific to this component and not a general problem with the QClaw Gateway or the model.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

NOT_ENOUGH_INFO

#memory management#API rate limit#retriever error#indexing error#inference speed

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Control UI: Thinking icon disappears after ~1 minute and conversation goes blank (webchat channel) [1 comments, 2 participants]