Feature Request: Allow customizing or renaming session/tab names

Feature Request: Allow customizing or renaming session/tab names

Problem

When using slash commands like /start, the session name defaults to the command name (e.g., "/start"). This makes it difficult to distinguish between multiple sessions when working on different tasks or projects.

Current Behavior

• Running /start creates a session named "/start"
• All sessions using /start have the same generic name
• No apparent way to manually rename sessions after creation
• Difficult to organize and identify sessions when multiple are open

Desired Behavior

One or more of the following options would be helpful:

1. Manual Session Renaming

• Right-click on session tab → "Rename Session"
• Keyboard shortcut to rename current session
• Command palette action: "Rename Current Session"

1. Session Name Customization in Commands

• Allow slash commands to specify a session name
• Example: /start --name "Xxxxxx Error Handling"
• Or use command description as session name

1. Auto-generated Smart Names

• Use first user message content as session name
• Use current task/context as session name
• Allow configuration of naming patterns

1. Session Name Template Configuration

• Add config option in .claude/config.json or similar
• Example: "sessionNameTemplate": "{command} - {timestamp}"
• Support variables like {project}, {branch}, {command}

Use Cases

• Working on multiple features/bugs simultaneously
• Distinguishing between different projects in monorepo
• Organizing sessions by task type (feature, bugfix, refactor)
• Quickly identifying which session contains specific work

Example Scenario

Currently:

/start  (fixing authentication bug)
/start  (adding new feature)
/start  (code review)

Desired:

Fix Auth Bug
Add User Dashboard
Code Review - PR #123

Workaround Attempted

• Creating custom slash commands with descriptive names (e.g., /start-feature, /start-bugfix)
• This helps but requires creating many similar commands
• Still limited to command name length and format

Proposed Solution Priority

1. High Priority: Manual session renaming (simplest to implement, most flexible)
2. Medium Priority: Session name configuration in slash commands
3. Nice to Have: Auto-generated smart names based on context

Additional Context

This feature would significantly improve the developer experience when managing multiple Claude Code sessions, especially for developers who:

• Work on multiple tasks in parallel
• Context-switch frequently between projects
• Use Claude Code as their primary development assistant

Related Issues

• (If any exist, link them here)

Environment

• Claude Code version: (latest as of January 2026)
• Platform: macOS (but likely applies to all platforms)