Preflight Checklist
Problem Statement
On Windows, the Cowork folder picker restricts project folder selection to directories under the user profile (C:\Users\<username>\). Claude Code's folder picker does not have this restriction — it allows any accessible path on the filesystem.
This is a problem for users who store projects on secondary drives, NAS mounts, or organizational paths outside the user profile (e.g., D:\Projects\, E:\Work\, or network-mapped drives). The restriction appears to be a Cowork desktop UI implementation choice rather than a platform limitation, since Claude Code (which shares the same base) does not enforce it.
Proposed Solution
Remove the user-profile-directory restriction from the Cowork folder picker on Windows. Allow users to select any directory they have read/write access to, matching Claude Code's behavior.
If there is a security or sandboxing reason for the restriction, consider:
- Allowing users to configure additional trusted root paths in settings
- Displaying a confirmation prompt when selecting folders outside the user profile
- At minimum, documenting the restriction and the rationale
Alternative Solutions
Moving the project folder under C:\Users\<username>\ works but forces an unnatural directory structure. Users with existing organizational systems, version-controlled repos on other drives, or shared network storage should not need to restructure their filesystem to accommodate a UI limitation that doesn't exist in Claude Code.
Priority
High - Significant impact on productivity
Feature Category
Configuration and settings
Use Case Example
- I have a multi-project writing system stored at
D:\Projects\Republic\ (outside my user profile).
- I open Cowork and click "Add project folder."
- The folder picker only shows directories under
C:\Users\mike\. I cannot navigate to D:\.
- I am forced to either move my entire project tree under my user profile or create symlinks — neither of which should be necessary.
- Meanwhile, Claude Code lets me open
D:\Projects\Republic\ with no restrictions.
Platform: Windows 11. This may not affect macOS/Linux — needs verification.
Additional Context
No response
Preflight Checklist
Problem Statement
On Windows, the Cowork folder picker restricts project folder selection to directories under the user profile (
C:\Users\<username>\). Claude Code's folder picker does not have this restriction — it allows any accessible path on the filesystem.This is a problem for users who store projects on secondary drives, NAS mounts, or organizational paths outside the user profile (e.g.,
D:\Projects\,E:\Work\, or network-mapped drives). The restriction appears to be a Cowork desktop UI implementation choice rather than a platform limitation, since Claude Code (which shares the same base) does not enforce it.Proposed Solution
Remove the user-profile-directory restriction from the Cowork folder picker on Windows. Allow users to select any directory they have read/write access to, matching Claude Code's behavior.
If there is a security or sandboxing reason for the restriction, consider:
Alternative Solutions
Moving the project folder under
C:\Users\<username>\works but forces an unnatural directory structure. Users with existing organizational systems, version-controlled repos on other drives, or shared network storage should not need to restructure their filesystem to accommodate a UI limitation that doesn't exist in Claude Code.Priority
High - Significant impact on productivity
Feature Category
Configuration and settings
Use Case Example
D:\Projects\Republic\(outside my user profile).C:\Users\mike\. I cannot navigate toD:\.D:\Projects\Republic\with no restrictions.Platform: Windows 11. This may not affect macOS/Linux — needs verification.
Additional Context
No response