Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: [BUG] UI shows agent "running" after conversation ends — requires manual page refresh every time

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…

Every conversation turn, the Control UI shows the agent as "running" even after the turn has completed. User must manually refresh the page to start a new conversation.

Root Cause

Every conversation turn, the Control UI shows the agent as "running" even after the turn has completed. User must manually refresh the page to start a new conversation.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Every conversation turn, the Control UI shows the agent as "running" even after the turn has completed. User must manually refresh the page to start a new conversation.

Steps to reproduce

  1. Send any message to the agent
  2. Wait for agent to respond and complete
  3. Observe: UI still shows "running" state, no new turns possible without refresh
  4. Refresh page → normal behavior resumes until next turn

Expected behavior

After an agent turn completes, UI should immediately show "idle" state without requiring a page refresh.

Actual behavior

Gateway and agent are functioning correctly — only the UI state update is broken

  • Tested with multiple conversation turns, issue is 100% reproducible
  • Process appears to complete (exec exits, tokens counted) but UI doesn't reflect completion
  • Sessions list still shows "running" for completed sessions

OpenClaw version

2026.5.27

Operating system

Windows 10 (x64)

Install method

npm

Model

minimax2.7

Provider / routing chain

https://api.minimaxi.com

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

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

After an agent turn completes, UI should immediately show "idle" state without requiring a page refresh.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING