claude-code - 💡(How to fix) Fix Allow renaming session titles in the VS Code extension

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fix / Workaround

  • Workaround I use today: I try to make my very first message in a new session double as the title (e.g., "Refactor auth middleware — keep this as the title"), but this is awkward and pollutes the actual conversation.
  • Considered: searching the session list by content instead of renaming, but search doesn't help when I'm scanning visually to pick from recent sessions.
  • Considered: keeping a separate notes file mapping session IDs to descriptions — too much friction to maintain.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

Problem Statement

Session titles in the Claude Code VS Code extension are auto-generated from the first message of the conversation, and there's no way to edit them afterward. This makes it hard to find specific sessions later — especially for long-running work that evolved beyond what its first message described, or when several sessions in the same project end up with similar-looking auto-generated titles. I often have to open sessions one by one just to figure out which one I want.

Proposed Solution

Add a "Rename" action to each session in the VS Code extension's session list:

  • Right-click a session → "Rename", or a hover action / inline edit on the title
  • Typing a new name updates it immediately and persists across reloads
  • The custom title should be the same one shown if I open that session via the CLI (claude --resume), so naming stays consistent across surfaces
  • Clearing the custom title should fall back to the auto-generated one

Alternative Solutions

  • Workaround I use today: I try to make my very first message in a new session double as the title (e.g., "Refactor auth middleware — keep this as the title"), but this is awkward and pollutes the actual conversation.
  • Considered: searching the session list by content instead of renaming, but search doesn't help when I'm scanning visually to pick from recent sessions.
  • Considered: keeping a separate notes file mapping session IDs to descriptions — too much friction to maintain.

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

  • Platform: VS Code extension on Windows 11
  • Related surface: the same renamed title should show up when listing/resuming sessions from the claude CLI, so naming is consistent across the extension and terminal.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Allow renaming session titles in the VS Code extension