2 people reported
All time, since Sep 24.
Mapped network drive not in shell
“The shell does not: every device_bash call fails immediately with”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/622/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Mapped network drive never mounted into Cowork shell. On Windows, a mapped drive attached via folder picker works with file tools, but shell commands cannot see it.
Is this your bug?
File my report- Where
- Cowork sandbox shell
- Error text
None of the connected folders can be mounted into the workspace (e.g. network drives). Use device_stage_files / device_commit_files instead.- Versions
- 2.1.280
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Original reports2, newest first
- Cowork (Windows, cloud session): mapped network drive attached via folder picker works with file tools but is never mounted into the sandbox shell — breaks NAS workflows before Oct 6 removal of local-only mode#98459
- [Desktop App 3P] Mapped network drive is attached to the VM but never exposed to the session shell (Windows)#96810