Feature Request: Renamable/Named Sessions in Claude Code Extension

[MrCalebH]

Problem

When running multiple Claude Code sessions (either in separate windows or switching between contexts), there's no way to distinguish them. The extension tab is always just called "Claude Code" regardless of what you're working on.

For power users managing multiple projects, clients, or contexts simultaneously, this creates friction - you have to click into each session to remember what it was for.

Proposed Solution

Allow users to name/rename their Claude Code sessions. This could manifest as:

1. Renamable tab - Right-click the Claude Code tab → "Rename Session" → custom label shows in tab
2. Session selector - Multiple named sessions within a single Claude Code panel (tabs within the extension)
3. Workspace-aware naming - Automatically append the workspace/folder name to the tab (e.g., "Claude Code - MyProject")
4. Persistent session labels - Set a label at the start of a session that persists and displays in the tab title

Use Cases

• Running separate sessions for different projects
• Distinguishing between "research" vs "execution" contexts
• Managing client work separately from personal projects
• Multi-context workflows where you need to quickly switch between sessions

Additional Context

This is particularly relevant as Claude Code becomes more powerful for agentic workflows. Users spinning up multiple agents or working across contexts need quick visual identification of which session is which.

Even a simple /name or /label command that sets a display name would solve this elegantly.

---

Submitted via Claude Code

[github-actions]

Found 3 possible duplicate issues:

1. [FEATURE] Rename tabs in VS Code Extension #11145
2. [FEATURE] Delete and rename chats in VS Code extension #10747
3. [FEATURE] "Allow renaming conversation tabs" #16926

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[MattStarfield]

+1 - Adding CLI perspective on this same problem

I'm hitting the exact same issue but from the CLI side with claude --resume.

My Setup

• Raspberry Pi 5 running 10+ simultaneous Claude Code sessions via tmux
• Multiple sessions often target the same project but handle different tasks
• Building automated session recovery for system reboots

The CLI Problem

When running claude --resume, I see:

? Select a conversation to resume:
▸ 2026-01-11 12:50 - "I've noticed a very disturbing development..." (hapimatic-private)
  2026-01-11 11:28 - "Earlier today I had several terminal tabs..." (hapimatic-private)  
  2026-01-11 10:15 - "We need to implement session persistence..." (hapimatic-private)

Four sessions from the same project, all different tasks (security audit, crash investigation, feature implementation, bug fix). The truncated first message doesn't distinguish them.

Suggested CLI Enhancements

Building on this feature request, the CLI could benefit from:

1. /rename slash command - works in both IDE and CLI
2. Named sessions in --resume picker - show custom name instead of first message
3. --resume "name" support - resume by custom name, not just session ID
4. Session ID visibility - even partial IDs (abc123...) would help for scripting

Current Workaround

Starting sessions with distinctive first messages:

[PROJECT: hapimatic-private | TASK: tmux-persistence] Working on...

This is fragile and doesn't help existing sessions.

Why This Matters for Automation

I'm building session recovery scripts that save Claude session IDs and use claude --resume <session-id> for direct resume after reboots. When automated recovery fails, manually identifying the right session among many similar ones is painful.

If session names were stored in the .jsonl metadata, recovery scripts could display human-readable names instead of UUIDs.