[FEATURE]: Show pending review indicator for sessions needing attention #27772

Activity

1. github-actions

   assigned

   Hona

   on May 15, 2026
2. github-actions commented on May 15, 2026

   

   github-actionsBot

   on May 15, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [FEATURE]: notification when a session stops to ask a question #13532: Feature request for notification when a session stops to ask a question (same problem: sessions waiting for user input are not visually distinct)
   • [FEATURE]:Display status indicators (active/stopped/awaiting feedback) directly on agent avatars, without requiring hover to view. #12077: Feature request for displaying status indicators (active/stopped/awaiting feedback) on agent avatars (same solution concept: visual indicators for session state)

   Please review these issues and consider whether your request adds something new beyond what is already tracked.
3. allracs commented on Jun 8, 2026

   

   allracs

   on Jun 8, 2026

   Author

   More actions

   The dot is useful, but I would make the state behind it a little stricter than "session has unread output."

   For this workflow, I would split at least these states:

   • waiting_for_user_input
   • waiting_for_permission
   • still_running
   • completed_with_unread_output
   • stale_or_disconnected

   The important part is that the dot should be backed by a live session/request id, not just by last activity time. Otherwise a completed session with new logs and a blocked session that needs the user can collapse into the same visual signal.

   I maintain Faryo, where the same distinction is the core receipt: the phone/project workbench can show a pending action, but it only counts when the same live tmux-backed session consumes it: https://github.com/Snailflyer/faryo/releases/download/v1.0.7/faryo-public-redacted-same-session-handoff-walkthrough-20260528-0120.gif

   Thanks for the heads up! @Snailflyer
   I also thought of something like that already, but I wasn't sure if it would've mean a big re-structure, tho I'll try to look into it this week and give it a try 😉
4. github-actions commented on Aug 8, 2026

   

   github-actionsBot

   on Aug 8, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
5. github-actions

   closed this as not plannedon Aug 8, 2026