Summary
Define a more consistent way for the TUI to surface transient feedback, and reduce duplication between the status line, chat, and future notification UI.
Problem
Feedback in the TUI is currently spread across multiple places, such as the status line and chat, and future notification UI could add another channel. Without a clear model, the same event may appear in multiple places or be easy to miss.
Goal
Explore a few options for how the TUI should present transient feedback in a more consistent way.
This should include:
- where transient notifications should appear
- which events belong in notifications versus status line versus chat
- how to reduce duplicated feedback across those channels
Expected outcome
Settle on a notification model that is clear, consistent, and suitable for the TUI, potentially including a bottom-right notification area similar to the web UI.
Notes
A useful reference is the web UI notification pattern, but the TUI may need different tradeoffs because of limited terminal space.
Summary
Define a more consistent way for the TUI to surface transient feedback, and reduce duplication between the status line, chat, and future notification UI.
Problem
Feedback in the TUI is currently spread across multiple places, such as the status line and chat, and future notification UI could add another channel. Without a clear model, the same event may appear in multiple places or be easy to miss.
Goal
Explore a few options for how the TUI should present transient feedback in a more consistent way.
This should include:
Expected outcome
Settle on a notification model that is clear, consistent, and suitable for the TUI, potentially including a bottom-right notification area similar to the web UI.
Notes
A useful reference is the web UI notification pattern, but the TUI may need different tradeoffs because of limited terminal space.