[Feature Request] Agent view: Add directory display and directory-based grouping for sessions

Status Fixed / completed
Reported on v2.1.222
Maintainer reply None cached
Activity 2 comments · opened Aug 8, 2026 · closed Aug 17, 2026

Bug Description
Feedback on the agent view (background sessions overview, opened with ← / claude agents): As a user who mostly runs ONE foreground session per tmux tab, this screen is very hard to use. Two concrete problems: 1. No directory/path shown per session. Rows only show an auto-generated summary. I cannot tell which project/directory each session belongs to. The working directory is the most reliable way to identify a session — please show each session's cwd/path in the list (or at least an option to show it), not just in the /resume picker after Ctrl+A. 2. Grouping ONLY by state is unusable for memory. Sessions are grouped by Needs input / Working / Completed. State changes constantly, so a session jumps between groups and moves up/down. I can never remember "which one is where." Please add at least a second view: sort/group by DIRECTORY (stable), in addition to the state-based view. Also: the auto-generated summary is often wrong/stale, because a long session drifts across many unrelated topics — a one-line summary latched onto the opening question no longer matches what the session is about. This makes rows even harder to tell apart. Net effect: a newbie who accidentally presses ← lands here totally confused, with near-identical rows (I currently have two rows both literally titled "Identify WeChat account user") and no way to distinguish them. The only workaround I found is to enter each session and /rename it myself — which should probably be surfaced as the first suggested step. Suggestions: - Show per-session working directory/path in the list. - Offer a directory-based sort/group, not only state-based. - Nudge users to name sessions (/rename) since auto-summaries are unreliable.

Environment Info

  • Platform: darwin
  • Terminal: xterm-256color
  • Version: 2.1.222
  • Feedback ID: 7b07a438-39b9-44cb-9e67-2b464e9ecf99

Errors

[]

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗