Description
When using OpenClaw TUI, the streaming status indicator continues for 30-120+ seconds after the response content finishes. Users cannot tell when the response is complete.
Expected
TUI should show idle promptly after last content token.
Actual
Status bar shows streaming for 30-120+ seconds after text stops updating.
Root Cause
Delay between model finishing and gateway emitting chat final event. Post-run work (session persistence, delivery, cleanup) extends the visible streaming state.
Environment
- OpenClaw v2026.4.9, Ubuntu 24.04.4, Claude Opus 4.6, openclaw tui
Suggestion
- Emit content-complete signal separate from lifecycle end
- Or TUI shows finishing status when no new delta arrives
Description
When using OpenClaw TUI, the streaming status indicator continues for 30-120+ seconds after the response content finishes. Users cannot tell when the response is complete.
Expected
TUI should show idle promptly after last content token.
Actual
Status bar shows streaming for 30-120+ seconds after text stops updating.
Root Cause
Delay between model finishing and gateway emitting chat final event. Post-run work (session persistence, delivery, cleanup) extends the visible streaming state.
Environment
Suggestion