fix(tui): clarify streaming status

[BunsDev]

Summary

• replace the vague streaming fallback with Waiting on network
• surface stalled streams as Stalled — check connection, Ctrl+C to interrupt instead of only recoloring the spinner
• share stall detection between status text and spinner color, and render a status row during active streams

Verification

• cargo test -p claurst-tui streaming_status_label_falls_back_through_text_then_thinking && cargo test -p claurst-tui streaming_status_label_explains_stalled_streams
• cargo fmt -p claurst-tui --check
• git diff --check
• cargo test -p claurst-tui
• cargo check -p claurst

Fixes #57

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Jun 11, 2026 3:29am

[Copilot]

Pull request overview

This PR improves TUI streaming-status clarity by replacing the vague default “Thinking” status with a more actionable “Waiting on network”, and by surfacing stalled streams with an explicit message (not just a spinner color change).

Changes:

• Introduces shared stall detection (stream_is_stalled) and uses it for both spinner coloring and status text.
• Updates streaming fallback label to “Waiting on network” and adds an explicit stalled-stream label.
• Adjusts status-row rendering logic so the status row is rendered during active streaming, and updates/extends tests accordingly.

Comments suppressed due to low confidence (1)

src-rust/crates/tui/src/render.rs:2217

• should_render_status_row now always returns true for app.is_streaming, which makes interesting_stream_status and its placeholder-filtering redundant (the variable no longer affects the outcome). Simplifying avoids unnecessary per-frame work and keeps the intent clear.

fn should_render_status_row(app: &App) -> bool {
    let interesting_stream_status = app
        .status_message
        .as_deref()
        .map(|status| {

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.