[FEATURE] Cowork/Code: Relocatable project folders without breaking configuration

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

Moving a Cowork or Claude Code project folder to a different location on disk (e.g., renaming a parent directory, migrating to another drive, or restructuring a project hierarchy) breaks the project binding. Configuration, conversation history, CLAUDE.md associations, and project settings all reference the original absolute path.

This makes project folders fragile. Any reorganization of the filesystem requires manually reconfiguring the project from scratch — re-adding the folder, losing conversation history, and re-establishing settings. For users who maintain evolving project structures, this is a recurring source of friction.

Proposed Solution

Support relocating project folders without breaking their configuration. Two possible approaches:

1. Project-local identity: Store a unique project ID inside the project folder itself (e.g., in .claude/project.json). When a folder is added or detected, match by ID rather than path. If the path has changed, update the binding automatically.

1. Manual re-link: Provide a UI action to re-associate an existing project configuration with a new folder path, preserving conversation history, settings, and CLAUDE.md links.

Either approach decouples project identity from filesystem location — which is essential for any project system that expects to last.

Alternative Solutions

Currently there is no workaround. Moving a folder means starting over: re-add the project, lose conversation history, reconfigure settings. The .claude/ directory travels with the folder, but the application-level binding does not follow it.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

1. I have a Cowork project bound to C:\Users\mike\(0) TRP\(a) TRO\.
2. I decide to reorganize my project hierarchy — renaming (0) TRP to Republic or moving it to a different drive.
3. After the move, Cowork no longer recognizes the project. The sidebar entry is gone or broken.
4. I have to re-add the folder as a new project, losing all conversation history and settings.
5. With relocatable folders, Cowork would detect the .claude/ directory at the new path, match the project ID, and automatically update the binding.

Additional Context

_No response_