[FEATURE] Session history picker: allow renaming sessions in VS Code extension

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Problem

In the VS Code extension, the session history picker shows "This session is being continued from a previous conversation..." as the title for all continued sessions. This is especially problematic when forking a conversation — all forks start with the same auto-generated continuation summary, so they all get identical titles in the history picker. There is no way to tell them apart.

The /rename command exists in the terminal CLI version of Claude Code but is not available in the VS Code extension (Unknown skill: rename).

Steps to reproduce

1. Have a long conversation that hits context limit → it gets compacted + continued
2. Fork the continued session (start a new session from the same point)
3. Open the session history picker → all forks show the same title: "This session is being continued from a previo..."
4. No way to distinguish which fork is which

Expected behavior

Users should be able to rename/label sessions directly from the VS Code extension, either:

• Via right-click context menu in the session history picker
• Via a /rename slash command (parity with terminal CLI)
• Via inline editing of the session title in the picker

Current workaround

Manually tracking sessions by message count and timestamp — not scalable.

Environment

• Claude Code VS Code extension
• macOS

Related issues

• #24090 (Renameable session tabs in VS Code extension)
• #26121 (Session name lost after context compaction)
• #25870 (--session-name flag)

Proposed Solution

Proposed solution

Bring /rename command to the VS Code extension (parity with terminal CLI), and display the custom name in the session history picker. This way forked sessions can be labeled immediately after branching, before context is lost.

Optionally: auto-prompt for a session name when a continuation session is created (i.e. after context compaction), since that is the exact moment when forks become indistinguishable.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

_No response_