Detailed Analysis
A Claude Desktop user has surfaced a meaningful usability gap in Anthropic's Cowork feature: once a Cowork project is initialized against a specific local folder, there is no built-in mechanism to relocate that folder without starting the project over from scratch. The user created several Cowork projects tied to a local drive on a desktop machine, only to later decide they needed those projects accessible on a second laptop — requiring the files to live in a synced location like iCloud Drive. The core frustration is that reconstructing a project from scratch would mean forfeiting the accumulated conversational memory and context that makes the project valuable in the first place, while also fragmenting or duplicating conversation history across old and new project instances.
The research context confirms that no native folder-migration feature exists in Cowork as of April 2026. Cowork projects are architected as local workspaces bound at creation time to a chosen directory, using setup pathways such as "Start from scratch," "Use an existing folder," or "Import from a Claude project." The binding appears to be hard-coded at initialization, with no exposed setting to update the path post-creation. The only practical workaround is manual: create a new Cowork project pointed at the target folder, copy all contents from the original directory, and re-import any Claude-specific artifacts. This preserves the file data but does not cleanly transfer the project's built-up memory or conversation history — precisely the components the user identifies as most valuable and hardest to rebuild.
The friction described here reflects a broader architectural tension common to locally-anchored productivity tools. Projects in tools like RStudio or Visual Studio workspaces have faced nearly identical challenges, where folder relocation requires either file-level workarounds or re-initialization sequences rather than a simple path-update dialog. What makes the Cowork situation more acute is the AI-specific layer: unlike a code project that is fully reconstituted from its files, a Cowork project's value is partly stored in Claude's accumulated context and memory — state that is not simply a file on disk and cannot be trivially exported and re-imported. This creates a class of project data with no clear portability story.
The user's feature request — a formal folder-migration option — points to a real product gap as Cowork matures. Open issues on Anthropic's GitHub repositories for Claude Code show related requests around default workspace paths and folder handling that remain unresolved, suggesting this is a known but deprioritized area. As Anthropic positions Cowork for professional workflows where continuity and portability are table-stakes requirements, the inability to gracefully relocate a project's underlying folder represents a meaningful barrier to adoption in multi-device or team environments. A native "move project folder" option, analogous to how cloud-synced tools handle library relocation, would substantially reduce the friction of managing long-running Cowork projects across changing storage configurations.
Read original article →