[BUG] Cowork does not mount user's `.claude` folder when selected as working directory (Windows)
Resolved 💬 2 comments Opened Mar 9, 2026 by Heliomance Closed Apr 6, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When the user's .claude configuration directory is selected as the Cowork working folder, the VM does not mount it. Instead, the path /sessions/*/mnt/.claude/ points to the VM's own internal .claude directory. The host folder's contents are completely inaccessible, and files written by the VM do not persist to the host.
What Should Happen?
The host .claude folder should be mounted into the VM, with all its contents visible and writable.
Error Messages/Logs
Steps to Reproduce
- Open Claude Desktop on Windows
- Select the user
.claudefolder (e.g.C:\Users\<user>\.claude) as the Cowork working directory - The host folder contains user-created subdirectories and files beyond Claude's internal ones
- Inside the VM, run
ls -la /sessions/*/mnt/.claude/
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.68 (Claude Code)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗