[BUG] Session name shared across sessions in the same directory

Resolved 💬 2 comments Opened Mar 13, 2026 by rtky Closed Apr 11, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Bug: Session name shared across sessions in the same directory

When two sessions are open in the same project directory and one is renamed
(e.g. via /rename session1), /status shows the same name in both sessions,
even though their session IDs differ.

### Steps to reproduce

  1. Open two separate Claude Code sessions in the same directory
  2. Rename one session: /rename session1
  3. Run /status in both sessions

### Expected behavior
Each session has its own independent name tied to its session ID.

### Actual behavior
Both sessions show session1 despite having different session IDs.

## Feature request: Per-session naming

Session name should be a property of the session ID, not the project folder.
This is especially problematic with forks — branched sessions would all share
the same name with no way to distinguish them.

### Suggested improvement

  • Store session name against the session ID, not the directory
  • /status should show the session's own name
  • For forks, show lineage (e.g. session1 > fork1)

What Should Happen?

### Expected behavior
Each session has its own independent name tied to its session ID.

Error Messages/Logs

Steps to Reproduce

### Steps to reproduce

  1. Open two separate Claude Code sessions in the same directory
  2. Rename one session: /rename session1
  3. Run /status in both sessions

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.74 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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