claude-code - 💡(How to fix) Fix /rename command unavailable in VS Code extension — session tabs cannot be renamed [2 comments, 1 participants]

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…
GitHub stats
anthropics/claude-code#47802Fetched 2026-04-15 06:41:55
View on GitHub
Comments
2
Participants
1
Timeline
7
Reactions
0
Participants
Timeline (top)
labeled ×3commented ×2closed ×1renamed ×1

Root Cause

  • 20+ issues filed about this across CLI, extension, and desktop — clear community demand
  • #33637 and #43511 were closed as COMPLETED for VS Code, but the feature does not work
  • CLI users have a working /rename; extension users have no equivalent
  • Power users managing multiple sessions (scheduled tasks, parallel features, debugging) cannot distinguish tabs
RAW_BUFFERClick to expand / collapse

Problem

The /rename slash command works in the Claude Code CLI (terminal) but is not available in the VS Code extension. There is no way to rename session tabs in the extension — not via slash command, not via right-click context menu, and not via any other UI element.

When working on multiple parallel sessions (feature work, debugging, reviews), the auto-generated tab names are generic and indistinguishable. This makes it very difficult to navigate between sessions.

Current behavior

  • CLI (terminal): /rename My Session works correctly, name displays in prompt bar
  • VS Code extension: /rename is not recognized as a command. Session tabs show auto-generated names only with no option to change them.

Expected behavior

  • /rename <name> should work in the VS Code extension
  • Alternatively: right-click on a session tab → "Rename" option
  • Renamed session names should persist across restarts, compaction, and /clear

Prior issues (all closed without resolution for the extension)

Several issues have been filed about this. Some were closed as "duplicate" pointing to CLI-only fixes, others as "stale/not planned":

Feature requests (VS Code extension specific):

  • #17536 — Renamable/Named Sessions in Claude Code Extension (NOT_PLANNED, stale)
  • #9198 — Rename conversation titles in VS Code extension (DUPLICATE)
  • #15050 — Rename conversations in VS Code sidebar (DUPLICATE)
  • #24090 — Renameable session tabs in VS Code (NOT_PLANNED, stale)
  • #24472 — /rename slash command support in VS Code (closed)
  • #25488 — Rename conversation/session tabs in VS Code (closed)
  • #25757 — Rename Claude Code tab titles in VS Code (closed)
  • #28679 — Rename conversation tabs in VS Code (closed)
  • #29895 — "Rename Session" command in VS Code (DUPLICATE)
  • #33637 — Rename session titles in VS Code (COMPLETED — but not working)
  • #43511 — Rename conversation tabs in VS Code (COMPLETED — but not working)

Desktop app:

  • #38207 — Allow renaming active sessions in desktop app (DUPLICATE)
  • #46155 — Rename conversations in desktop app (DUPLICATE)

Bug reports about /rename not persisting (cross-platform):

  • #34411 — VS Code: renamed sessions revert to original name
  • #37579 — VS Code doesn't restore renamed session titles
  • #23964 — /rename names not persisted to disk (fixed for CLI)
  • #47197 — /rename name lost after process exit (fixed for Windows CLI)

Why this matters

  • 20+ issues filed about this across CLI, extension, and desktop — clear community demand
  • #33637 and #43511 were closed as COMPLETED for VS Code, but the feature does not work
  • CLI users have a working /rename; extension users have no equivalent
  • Power users managing multiple sessions (scheduled tasks, parallel features, debugging) cannot distinguish tabs

Environment

  • Claude Code VS Code Extension (latest)
  • Windows 11 / macOS / Linux (platform-independent)
  • Claude Code CLI /rename works correctly on the same machine

extent analysis

TL;DR

The most likely fix for the issue of the /rename slash command not working in the VS Code extension is to implement the command in the extension, potentially by porting the existing CLI functionality.

Guidance

  • Review the code changes made for issues #33637 and #43511, which were closed as COMPLETED but do not seem to be working, to understand what might have gone wrong.
  • Investigate how the /rename command is handled in the CLI and consider porting this functionality to the VS Code extension.
  • Check the extension's code for any platform-specific limitations or differences that might be causing the issue.
  • Verify that the issue is not related to the extension's configuration or settings, and that the /rename command is properly registered and handled.

Example

No code snippet can be provided without more information about the extension's codebase, but an example of how the /rename command might be implemented in the extension could involve adding a command handler that updates the session tab's name.

Notes

The issue seems to be specific to the VS Code extension, and the fact that the /rename command works in the CLI suggests that the functionality is possible. However, without more information about the extension's codebase, it is difficult to provide a more detailed solution.

Recommendation

Apply a workaround by implementing the /rename command in the VS Code extension, potentially by porting the existing CLI functionality, as this seems to be the most direct way to address the issue and provide the desired functionality to users.

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…

FAQ

Expected behavior

  • /rename <name> should work in the VS Code extension
  • Alternatively: right-click on a session tab → "Rename" option
  • Renamed session names should persist across restarts, compaction, and /clear

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 /rename command unavailable in VS Code extension — session tabs cannot be renamed [2 comments, 1 participants]