Better session names in /resume
Status Fixed / completed
Maintainer reply None cached
Activity 6 comments · opened Mar 27, 2026 · closed Aug 17, 2026
Problem
When using /resume to pick up a previous session, the session list is difficult to navigate because sessions lack descriptive names. It's hard to tell which session was about what without opening each one.
Proposed Solution
Automatically generate a short, descriptive name for each session based on the conversation content (e.g., a summary of the main task or topic). This would make it much easier to identify and resume the right session.
Example
Instead of showing generic/timestamp-based entries, the /resume list could show something like:
- "Refactoring auth middleware"
- "Fixing CI pipeline for deploy"
- "Adding dark mode support"
This would greatly improve the UX of session management.
Showing cached comments. Read the full discussion on GitHub ↗
5 Comments
This is the same request as #35921 (2r). Until auto-naming is built in:
+1 on this. The current experience when you've explicitly named sessions via
/renameis particularly frustrating -- the name is stored and visible once you're inside the session, but the/resumepicker doesn't surface it. So you end up guessing which session is which from truncated auto-summaries, opening them one by one until you find the right one, only to confirm it had the correct name all along.At minimum,
/resumeshould display and search by user-set session names. That alone would save a lot of friction for anyone who bothers to name their sessions.TerminalTabTitle already exists. I would expect the session to be automatically named the same (converted to kebab case) if no other name has been given
+1 - Also the naming could be simple option while starting claude. Like claude -name FeatureABC
Yes, this would be a very helpful feature. +1