Feature Request: Session Renaming in VS Code Extension

Feature Request: Session Renaming in VS Code Extension

Summary

Add the ability to rename sessions in the VS Code extension tab, similar to how it's done in the macOS Claude desktop app. This would display custom session names instead of UUIDs or conversation previews.

Current Behavior

Sessions are displayed with:

• UUID identifiers (e.g., "3bad5253-ad7f-45e2-8965-de0a738f598a")
• Or conversation preview text
• No way to customize the display name

Requested Behavior

• Right-click session tab → "Rename Session"
• Editable session name displayed in tab
• Persistent naming - names saved and restored across VS Code restarts
• Name appears in session list - both open tabs and session history

Use Cases

1. Workflow Management

Problem: When managing 5+ concurrent sessions, it's impossible to remember which UUID corresponds to which task.

Solution: Named sessions provide instant context:

• "Database Migration Debug" - immediately know this is the DB work
• "CSS Refactor - Header Component" - clear scope and focus
• "Production Hotfix - Auth Bug" - indicates urgency and topic

2. Session State Communication

Problem: No way to indicate session status when stepping away.

Solution: Use names to communicate state:

• "WAITING_FOR_USER - API Key Needed"
• "BLOCKED - Docker Issue"
• "READY_FOR_REVIEW - Payment Flow"
• "WIP - Testing Phase"

3. Project Organization

Problem: Multiple projects with multiple sessions each - mental chaos.

Solution: Naming convention reveals structure:

• "ClientA_Feature_Auth"
• "ClientA_Feature_Payment"
• "ClientB_Bugfix_Database"
• "Personal_Script_Backup"

4. Cognitive Load Reduction

Problem: Mental mapping of "session 3bad5253 = CSS work" is exhausting and error-prone.

Solution: Direct semantic mapping:

• See name → know context immediately
• No mental translation layer
• Reduces decision fatigue when context switching

5. Collaboration & Documentation

Problem: Screenshots and demos show cryptic session identifiers.

Solution: Professional, meaningful session names:

• Screenshots self-document with clear session names
• Session handoffs between team members more intuitive
• Audit trails become searchable ("find the payment bug fix session")

6. Accident Prevention

Problem: Easy to accidentally continue work in wrong session when all tabs look similar.

Solution: Clear, distinct names prevent mistakes:

• "Production Code Review" vs "Experimental Sandbox" - can't confuse them
• Visual scanning becomes reliable
• Reduces "oh no, I just edited the wrong file" moments

Real-World Workflow Example

Before (Current):

Open Tabs:
- 3bad5253...
- fae22ef8...
- 99662639...
- b2e60a57...

User thinks: "Which one was my database work? Let me click each one... oh wait, that's CSS... no that's the auth bug... ah here it is!"

After (With Renaming):

Open Tabs:
- Database Migration Debug
- CSS Header Refactor
- Auth Bug Investigation  
- Production Hotfix - Payment

User thinks: "Database Migration Debug" → clicks → immediate context.

Implementation Suggestions

UI/UX

1. Right-click context menu on session tab → "Rename Session"
2. Inline editing - click to edit directly in tab (like file renaming in VS Code)
3. Double-click to rename - familiar VS Code pattern
4. Character limit - 60 chars (prevents tab overflow)
5. Default naming - Falls back to UUID if no custom name set

Persistence

• Store in session metadata file (alongside JSONL transcript)
• Format: ~/.claude/projects/-Users-{user}/{uuid}.meta.json:

{
  "session_uuid": "3bad5253-ad7f-45e2-8965-de0a738f598a",
  "custom_name": "Database Migration Debug",
  "created_at": "2025-11-15T18:57:26Z",
  "last_renamed_at": "2025-11-17T15:45:00Z"
}

Display Behavior

• Tab title: Show custom name (or UUID if no name)
• Hover tooltip: Show both custom name + UUID for reference
• Session list: Custom name in sidebar, UUID in small gray text below
• Search: Allow searching by custom name OR UUID

Edge Cases

• Name conflicts: Allow duplicate names (users might want "Debug Session 1", "Debug Session 2")
• Empty name: Fall back to UUID
• Special characters: Allow alphanumeric + spaces + common punctuation (-, _, :, etc.)
• Session export: Include custom name in export metadata

Comparison to macOS Claude Desktop App

The macOS Claude desktop app already supports session renaming:

• Clean, intuitive interface
• Persistent across restarts
• Searchable by custom name
• Bring this same UX to VS Code extension for feature parity

Benefits Summary

✅ Instant context recognition - No mental mapping required
✅ Better project organization - Group sessions semantically
✅ Reduced cognitive load - Less mental energy per context switch
✅ Prevents accidents - Clear names reduce wrong-session errors
✅ Professional screenshots - Meaningful names in demos/docs
✅ Searchable sessions - Find by task, not UUID
✅ Session lifecycle tracking - Name evolves with session state (WIP → Review → Done)

Priority

High - This is a quality-of-life feature that significantly impacts daily workflow when managing multiple concurrent sessions.

Related

• macOS Claude desktop app session renaming (reference implementation)
• VS Code file renaming (similar UX pattern to follow)