Repository navigation
Closed as duplicate
Labels
duplicateThis issue or pull request already existsThis issue or pull request already exists
Description
Description:
Feature Description
Enhance the existing /resume command by adding the ability to assign custom names to conversations, making them easier to identify beyond just the session summary.
Current Behavior
The /resume command currently shows:
- Time since last activity
- Time created
- Number of messages
- Auto-generated summary of the session
While helpful, the summaries are often truncated and may not clearly indicate the project or context.
Proposed Enhancement
Add custom naming to complement the existing summary:
Current Display:
Modified Created # Messages Summary
- 53s ago 3h ago 29 This session is being continued from a previo...
- 14h ago 14h ago 491 This session is being continuing from a previo...
- 14h ago 14h ago 197 This session is being continued from a previo...
Proposed Display with Names:
Modified Created # Messages Name Summary
- 53s ago 3h ago 29 YouTube Automation This session is being continued...
- 14h ago 14h ago 491 main.py refactoring This session is being continuing...
- 14h ago 14h ago 197 API Documentation This session is being continued...
Implementation Options
Option 1: Add a /rename command for current session
> /rename "YouTube Automation Project"
Session renamed to: YouTube Automation Project
Option 2: Add naming flag when starting
claude --name "API Documentation" "Help me document this API"
Option 3: Inline rename during /resume
> /resume
[Shows current list]
> /resume --rename 1 "YouTube Automation"
Benefits
1. Quick Project Identification: Custom names immediately identify the project context
2. Better Than Summaries Alone: Summaries are often generic ("This session is being continued...")
3. Maintains Existing Workflow: Enhances rather than replaces current functionality
4. Project Organization: Multiple conversations for the same project can share naming conventions
Use Case Example
As shown in the screenshot, many sessions have similar generic summaries. With custom names:
- Session 1: "YouTube Automation" instead of relying on truncated summary
- Session 2: "main.py refactor" clearly indicates the file being worked on
- Session 3: "API docs" immediately identifies documentation work
Additional Context
- The current /resume interface is already excellent - this would enhance it further
- Names should be optional - unnamed sessions would display as they currently do
- This feature exists in Cursor AI and significantly improves session management
This better reflects the actual current functionality and proposes a clear enhancement to the existing `/resume`
command interface!
Reacted by Robert Dailey, _WD_, George, Ian Maurer, Isao Yoshikoshi, Jakub Sygnowski, Nathan, Andrew Shore, Ido Savion, Chris Penny and 6 more
Metadata
Metadata
Assignees
Labels
duplicateThis issue or pull request already existsThis issue or pull request already exists
Activity
sygi commentedon Jul 14, 2025
Related to this, it'd be great if claude knew the id/summary/anything about the currently-running session
shorea commentedon Jul 30, 2025
Would love this feature. To add to it, consider also exposing session names/summaries via some kind of --list-sessions/--list-conversations options. Being able to access this data via the CLI opens up some very powerful integrations with the shell like using fzf to fuzzy search sessions and quickly jump back to the project/conversation you want.
shorea commentedon Jul 31, 2025
If anyone is interested I've implemented a poor mans solution of this by leveraging their explicit session ID feature and writing custom names to a file. Using fzf you can fuzzy search by session name for the current project/directory (ccr) or all projects/directories (ccra). ccn allows you to create a new session with a custom name
ZSH
vlsi commentedon Aug 7, 2025
It would be great if the agent could update the conversation title as well. For instance, the instruction could be
Rename the conversation to "Review $ticketId for project $projectName ..."github-actions commentedon Aug 16, 2025
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
github-actions commentedon Aug 20, 2025
This issue has been automatically closed as a duplicate of #2112.
If this is incorrect, please re-open this issue or create a new one.
🤖 Generated with Claude Code
github-actions commentedon Aug 27, 2025
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.