anthropics
Add ability to name and organize conversation sessions
Feature Request: Named Sessions in Claude Code
Description:
Currently, Claude Code maintains conversation history and allows resuming previous sessions, but there's no way to assign custom names or labels to sessions. This makes it difficult to organize and quickly identify specific conversations, especially when working on multiple projects or tasks.
Specifically this should be available through the Visual Studio Code extension at least.
Proposed Feature:
Add the ability to:
- Name sessions - Allow users to assign custom names to conversation sessions (e.g., "Refactoring Auth System", "Bug Fix: API Timeout", "Learning React Hooks")
- Rename sessions - Edit session names after creation
- Session metadata - Display session name in the UI alongside timestamp
- Session search/filter - Filter or search sessions by name when resuming conversations
Use Cases:
- Project Organization: Working on multiple projects simultaneously and needing to switch between different conversation contexts
- Task Tracking: Maintaining separate sessions for different features, bugs, or refactoring efforts
- Team Collaboration: When sharing session references with teammates, named sessions are more meaningful than timestamps
- Long-term Reference: Finding specific conversations weeks or months later based on descriptive names rather than dates
Proposed Implementation Ideas:
- Add a "Session Name" field in the session header that can be clicked to edit
- Include session naming in the command palette (e.g.,
/rename-session [name]) - Show session names in the session resume/history interface
- Allow naming sessions at creation time or retroactively
Additional Context:
Similar features exist in other AI assistants (e.g., ChatGPT allows renaming conversations), and users frequently manage multiple concurrent development tasks where clear session identification would improve workflow efficiency.
Workarounds Attempted:
- Using memory features (
#shortcut) to tag sessions - Maintaining external notes mapping session IDs to projects
- Neither provides native UI integration or easy session discovery
totally agree the /resume naming convention is borderline unusable at times. especially when chats duplicate and multiple are named "conversation compacted...". Great request
+1 Same pain here — all my sessions after compact show identical "This session is being continued from a previous conversation..." names.
Session naming is a must-have.
It looks like this was added in 2.0.64:
Added named session support: use /rename to name sessions, /resume
in REPL or claude --resume from the terminal to resume them
BTW, this issue seems like a dup of #2112?
