Feature Request: Add Conversation Naming/Renaming Capability

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

1. 53s ago 3h ago 29 This session is being continued from a previo...
2. 14h ago 14h ago 491 This session is being continuing from a previo...
3. 14h ago 14h ago 197 This session is being continued from a previo...

### Proposed Display with Names:
Modified Created # Messages Name Summary

1. 53s ago 3h ago 29 YouTube Automation This session is being continued...
2. 14h ago 14h ago 491 main.py refactoring This session is being continuing...
3. 14h ago 14h ago 197 API Documentation This session is being continued...

## Implementation Options

### Option 1: Add a /rename command for current session
```bash
> /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!

!Image