openclaw - 💡(How to fix) Fix [Bug] WebChat: Stop button stuck in thinking state after response completes

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…

Fix Action

Workaround

Refreshing the page (Cmd+R on Mac) temporarily resolves the visual issue. The conversation functions normally after refresh.

RAW_BUFFERClick to expand / collapse

Bug Report: WebChat Stop Button Stuck in "Thinking" State

Severity

Low — UI display issue only; no impact on actual functionality or data

Environment

  • App: OpenClaw WebChat
  • Channel: webchat
  • Runtime: agent=main | host=MacBook Air | os=Darwin 25.3.0 (arm64) | model=minimax/MiniMax-M2
  • Browser: Safari
  • App Version: OpenClaw 2026.5.12 (50a2481)

Issue Description

The stop button in the WebChat interface remains in a "thinking" state after the assistant has fully completed its response and the session is idle. The button displays three animated dots (pulsing thinking indicator) and does not respond to clicks — it appears permanently stuck.

This has been observed multiple times within the same session.

Steps to Reproduce

  1. Open WebChat and send a message to the assistant
  2. Wait for the assistant to complete its response
  3. Observe that the stop button still shows the thinking animation (three pulsing dots) after the response is fully delivered
  4. Click the stop button — it does not respond or stop anything

Expected Behavior

Once the assistant has completed its response, the stop button should return to an idle/inactive state and should not display the thinking animation.

Workaround

Refreshing the page (Cmd+R on Mac) temporarily resolves the visual issue. The conversation functions normally after refresh.

Additional Notes

  • This appears to be a UI display bug only — the actual backend state is correct (the assistant has stopped processing), but the frontend button state does not refresh to reflect this
  • No data loss or functionality impact has been observed
  • A screenshot or screen recording of the issue would be helpful for debugging

Suggested screenshot/recording: Capture the stuck stop button animation alongside the completed response text in the chat area.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING