openclaw - ✅(Solved) Fix [Bug]: Streaming never ends (UI stuck) [1 pull requests, 1 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#63189Fetched 2026-04-09 07:57:15
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2

Bug: Streaming never ends (UI stuck)

  • Model: minimax/MiniMax-M2.7
  • Fast mode: on/off 都复现
  • Steps: Normal session
  • Expected: Streaming stops after response
  • Actual: Timer keeps going indefinitely
  • Workaround: Ctrl+C or send another message

Root Cause

Bug: Streaming never ends (UI stuck)

  • Model: minimax/MiniMax-M2.7
  • Fast mode: on/off 都复现
  • Steps: Normal session
  • Expected: Streaming stops after response
  • Actual: Timer keeps going indefinitely
  • Workaround: Ctrl+C or send another message

Fix Action

Fix / Workaround

Bug: Streaming never ends (UI stuck)

  • Model: minimax/MiniMax-M2.7
  • Fast mode: on/off 都复现
  • Steps: Normal session
  • Expected: Streaming stops after response
  • Actual: Timer keeps going indefinitely
  • Workaround: Ctrl+C or send another message

PR fix notes

PR #66289: fix(tui): resolve streaming status stuck indefinitely after run completes

Description (problem / solution / changelog)

Problem

Fixes #63189

The TUI streaming status indicator (⠼ streaming • xxxm xxs | connected) gets stuck forever after a response completes. The timer keeps counting indefinitely and the only workaround is Ctrl+C or sending another message.

Root Cause

In tui-event-handlers.ts, both finalizeRun() and terminateRun() only call setActivityStatus() when wasActiveRun is true. If the chat:final event arrives after activeChatRunId has already been cleared (e.g., by a lifecycle:end agent event or a concurrent run), wasActiveRun evaluates to false and the status remains stuck at "streaming".

Fix

Two-pronged approach for robustness:

1. Safety-net in finalizeRun / terminateRun (event-handlers)

When wasActiveRun is false but no active or pending session runs remain (activeChatRunId === null && sessionRuns.size === 0), unconditionally reset the activity status. This handles the race condition between lifecycle and chat events.

2. Streaming idle timeout (tui.ts)

Arms a 30-second safety timer whenever the TUI enters streaming or running state. Each incoming delta resets the timer. If no status update arrives within the window, the UI auto-resets to idle. This acts as a last-resort fallback for any scenario where the final event is lost entirely (e.g., WebSocket reconnect gap).

The timeout only applies to streaming and running states — sending and waiting are excluded since those pre-response phases can legitimately take longer.

Testing

  • All 22 existing TUI event handler tests pass ✅
  • Added 1 new test covering the runId-mismatch scenario (23 total) ✅

Changes

  • src/tui/tui-event-handlers.ts — safety-net idle reset in finalizeRun and terminateRun
  • src/tui/tui.ts — streaming idle timeout (30s) in setActivityStatus
  • src/tui/tui-event-handlers.test.ts — regression test for #63189

Changed files

  • src/tui/tui-event-handlers.test.ts (modified, +57/-0)
  • src/tui/tui-event-handlers.ts (modified, +10/-0)
  • src/tui/tui.ts (modified, +27/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Bug: Streaming never ends (UI stuck)

  • Model: minimax/MiniMax-M2.7
  • Fast mode: on/off 都复现
  • Steps: Normal session
  • Expected: Streaming stops after response
  • Actual: Timer keeps going indefinitely
  • Workaround: Ctrl+C or send another message

Steps to reproduce

normal session

Expected behavior

Streaming stops after response

Actual behavior

Timer keeps going indefinitely

OpenClaw version

2026.4.5

Operating system

ubuntu 24.04

Install method

No response

Model

Minimax M2.7 highspeed

Provider / routing chain

minimax official

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 of the streaming never ending and the UI getting stuck can be temporarily worked around by sending another message or using Ctrl+C to interrupt the process.

Guidance

  • Investigate the minimax/MiniMax-M2.7 model's behavior in fast mode to see if there's a specific condition causing the streaming to not stop after a response.
  • Verify if the issue persists across different operating systems or if it's specific to ubuntu 24.04.
  • Check the OpenClaw version 2026.4.5 documentation for any known issues related to streaming or the MiniMax model.
  • Consider testing with a different model or provider to isolate if the issue is model-specific or a broader problem.

Example

No specific code example can be provided without more details on the implementation, but reviewing the model's integration with the streaming service might reveal a logic error or missing termination condition.

Notes

The lack of logs, screenshots, and additional information makes it challenging to provide a more precise fix. The issue might be related to how the MiniMax model handles the end of a streaming session, possibly due to a regression introduced in the model or OpenClaw version 2026.4.5.

Recommendation

Apply workaround: Given the information, the best course of action seems to be using the provided workarounds (sending another message or Ctrl+C) until a more permanent fix can be identified and implemented.

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

Streaming stops after response

Still need to ship something?

×6

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

Back to top recommendations

TRENDING