claude-code - 💡(How to fix) Fix Duplicate session names when multiple sessions share the same git branch

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

Current workaround

RAW_BUFFERClick to expand / collapse

Problem

When opening multiple Claude Code sessions from the same git branch, all sessions get the exact same auto-generated name (the branch name). This makes it impossible to distinguish between sessions in the session list.

Example: Two sessions opened on branch ACME-00000/version-0-1-10 are both named ACME-00000/version-0-1-10.

Expected behavior

Session names should be unique. When a session name already exists, Claude Code should disambiguate — e.g., by appending a counter ((2), (3)) or a timestamp.

Current workaround

Manually renaming sessions, which shouldn't be necessary.

Environment

  • Claude Code on Windows 11
  • Multiple sessions opened from the same branch in the same repo

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

Session names should be unique. When a session name already exists, Claude Code should disambiguate — e.g., by appending a counter ((2), (3)) or a timestamp.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING