Detailed Analysis
Claude CoWork's project folder system presents a known limitation that affects users who reorganize their local file directories: moving a project folder severs the application's connection to that project entirely. When a folder is relocated, Claude Desktop loses track of the original path, resulting in the loss of conversation history, saved settings, memory configurations, and accumulated context. The project location dropdown in the CoWork interface becomes grayed out and non-editable for existing projects, which is precisely the behavior the Reddit user encountered — there is currently no built-in mechanism to simply redirect an existing project to a new folder path.
The recommended workaround, while functional, requires manual reconstruction. Users must navigate to Claude Desktop → CoWork → Projects and select the **"Use an existing folder"** option when creating a new project, then point it to the moved folder's new location. This approach preserves the underlying files themselves, since CoWork stores project documents locally and does not delete or alter them during a move. However, everything layered on top of those files — conversation history, custom instructions, memory, and project-level configurations — does not transfer and must be rebuilt from scratch. The distinction between the files (safe) and the project metadata (lost) is a critical one for users to understand before proceeding with any directory reorganization.
This behavior reflects a broader architectural reality of Claude CoWork in its current form: it is a desktop-only application with no cloud synchronization, meaning all project state is tightly coupled to local path references. Unlike cloud-native tools where project identity is tied to a persistent remote identifier, CoWork's project identity is anchored to a specific filesystem location. This makes the system fragile in the face of ordinary file management tasks that users routinely perform, such as restructuring directories or migrating to a new drive. The absence of a "relink folder" option in the UI — something that would resolve this entirely — is a notable gap.
The issue also intersects with other current limitations of the platform. CoWork projects are not yet shareable across Team or Enterprise plan accounts, and integration with Claude Code remains planned but unimplemented as of the current date. These constraints collectively suggest CoWork is still in a relatively early stage of development, with core infrastructure like path management and cross-device continuity not yet fully addressed. Community-reported issues on GitHub echo this, with users flagging the folder-move problem as a friction point with no official automated resolution. For now, users planning directory reorganization are best advised to document their project instructions and any important context before moving folders, treating the recreation step as a fresh project setup rather than a seamless migration.
Read original article →