[FEATURE] Allow relocating active sessions to a new working directory

Open 💬 7 comments Opened Feb 23, 2026 by yionis01

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

Currently, Claude sessions are permanently bound to the working directory where they were created. If you move project
files or reorganize folders, you cannot move the session's context with them—you must start a new session in the new
location and lose conversation history. This quickly creates a mess.

Proposed Solution

Add a command to relocate the current session:
/relocate /new/working/directory

This would:

  • Update the session's working directory metadata
  • Update the project path in sessions-index.json
  • Allow the session to continue seamlessly from the new location
  • Optionally move/update any file references in the session history

Alternative Solutions

/move-session ~/new/path

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

A user starts a session in ~/temp/project and builds up significant context (conversation history, file edits,
preferences). Later, they move the project to ~/projects/my-app/ but the session remains tied to the old path. The only
option is to start fresh and lose all context.

Additional Context

Why It Matters

  • Preserves conversation context during project reorganization
  • Supports common development workflows (moving repos, consolidating projects)
  • Reduces friction when directory structures change

View original on GitHub ↗

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