[FEATURE] Sync Claude Code session name with VS Code terminal name

Resolved 💬 5 comments Opened Jan 13, 2026 by hkkarnan-amzn Closed Apr 1, 2026

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

Feature Request

When using Claude Code in VS Code's integrated terminal, automatically sync the Claude Code session name when the user renames the terminal tab.

Use Case

I often run multiple Claude Code sessions in different VS Code terminals, each focused on a different task (e.g., "frontend-refactor", "api-bugfix", "tests"). To keep things organized, I rename my VS Code terminal tabs to reflect what I'm working on.

Currently, I have to manually run /rename <name> in Claude Code separately after renaming the terminal. It would be much more seamless if Claude Code's session name automatically updated to match the terminal name.

Proposed Solution

Proposed Behavior

  1. When a user renames their VS Code terminal tab, Claude Code detects this change
  2. The Claude Code session name automatically updates to match the new terminal name
  3. Optionally, this could be a configurable setting (e.g., syncSessionNameWithTerminal: true)

Possible Implementation

  • The VS Code extension could listen for terminal rename events via the VS Code API (onDidChangeTerminalState or similar)
  • When detected, send a signal to the running Claude Code process to update the session name
  • Alternatively, expose a new hook like TerminalRenamed that users could configure

Alternative Solutions

  • Manually running /rename after each terminal rename (current workaround, but cumbersome)
  • Always naming the Claude Code session first, then renaming the terminal to match

Additional Context

This would improve the multi-session workflow for users who organize their work across multiple terminals and want consistent naming between VS Code and Claude Code.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗