Bug type

Behavior bug (incorrect output/state without crash)

Summary

Description

TUI only shows user's input, no assistant reply at all. Content only appears after response completes. Opening WebUI during wait triggers the dump.

Environment

• OS: macOS 15.7.4 (24G517)
• Node: v24.7.0
• OpenClaw: 2026.3.2
• TUI: openclaw-tui
• Model: minimax-cn/MiniMax-M2.5
• Terminal: Apple Terminal / iTerm2

Environment

• TUI: openclaw-tui
• Model: minimax-cn/MiniMax-M2.5
• Gateway: Normal
• WebUI: Normal (displays streaming content in real-time)

Initial Analysis

1. Data is returned normally (otherwise content wouldn't appear at all)
2. Issue is in TUI's rendering layer
3. Possibly pi-tui buffer not flushed in time
4. WebUI access triggers some sync mechanism that forces TUI buffer flush

Additional Findings

• Both TUI and WebUI use the same Provider (anthropic-message format)
• TUI may have issues handling MiniMax's thinking block

Steps to reproduce

1. Open TUI: openclaw tui
2. Use MiniMax model (minimax-cn/MiniMax-M2.5) and send a message
3. Observe TUI output

Expected behavior

TUI should display assistant's reply (real-time or buffered)

Actual behavior

• TUI shows "running" status but no content appears
• After response completes, all content displays at once
• If WebUI is opened to view the same session while waiting, content "floods back" to TUI

OpenClaw version

OpenClaw: 2026.3.2

Operating system

• OS: macOS 15.7.4 (24G517) - Node: v24.7.0 - OpenClaw: 2026.3.2 - TUI: openclaw-tui - Model: minimax-cn/MiniMax-M2.5 - Terminal: Apple Terminal / iTerm2

Install method

npm -g

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response