[FEATURE] Sessions should follow a moved or renamed project folder (successor to #79215)

Status Open
Reported on v2.1.251
Maintainer reply None cached
Activity 1 comment · opened Sep 23, 2026

Successor to #79215 (Sessions should follow a renamed/moved project folder). Lifecycle automation closed it on 2026-09-18 with "Please open a new issue if this is still relevant". It is still relevant. #79215 was also the canonical issue for this request: A collaborator closed the Desktop-specific #88903 as its duplicate on 2026-08-25. #88903 was itself the successor to the stale-closed #55831. No open issue covers the request now, so this one carries both forward.

Problem

Claude Code identifies a project by its path-encoded working directory under ~/.claude/projects/. Renaming or moving the folder, a routine operation, orphans every existing session:

  • The Desktop sidebar keeps showing the old folder as a project group, and its sessions fail to resume ("folder is no longer available"). This was reported in #79215 on macOS and in #88903 on Windows.
  • The CLI's interactive --resume picker still requires changing into the session's directory first (reported on #28745 on 2026-09-14).
  • Desktop's per-session "change folder" action handles one session at a time and creates a fork with a new session ID rather than moving the session. This is as described in #79215; I have not re-tested it on the current build.

What already exists

  • claude --resume <session-id> finds a session from any directory, and /cd <path> re-homes the active session (#28745, closed as completed on 2026-08-17).
  • 2.1.251 fixed transcripts being overwritten when a directory change relocated a session onto an existing transcript with the same ID.

Neither moves historical sessions, and neither is reachable from Desktop. I checked the CLI CHANGELOG through 2.1.280, the Desktop changelog through 2.7032.0 (2026-09-22), and the Desktop documentation page by keyword. None mentions project identity, bulk session migration, rename detection, or a relocate action.

Requested

Any one of these, from most to least complete:

  1. Persistent project identity, for example a .claude/project-id file, with the session store keyed on the ID and the path stored as a mutable attribute.
  2. Rename detection: when a folder with no sessions matches a project whose recorded path is gone (same project ID or git remote), offer "Move N sessions to this folder".
  3. An explicit bulk move: a Desktop Relocate project action that lets the user pick the moved folder and keeps the session list, titles, and resume behaviour. A matching CLI command would cover the same case outside Desktop.

Environment

  • Windows 11, Claude Desktop 2.7032.0.0 (MSIX), bundled Claude Code
  • #79215 reported the same behaviour on macOS with Claude Code 2.1.214

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗