Summary

In TUI, pressing Enter and then immediately pressing Ctrl+C can show a local "canceled"-like status while the assistant reply still arrives.

This is confusing because Ctrl+C in TUI currently clears input / exits, but does not abort the active run (Esc or /abort does that).

Expected

When a run is active, Ctrl+C feedback should explicitly state that the run is still active and how to stop it.

Current behavior

• Ctrl+C updates local status for input/exit flow
• Users may interpret it as request cancellation
• Active run continues unless Esc or /abort is used

Proposed minimal fix

Update Ctrl+C status text to include an active-run hint:

• run still active (Esc or /abort to stop)

Scope / Safety

• UX text-only change in TUI
• No protocol/method changes
• No auth/security surface changes