[BUG] Suddenly cannot work from anetwork drive
Resolved 💬 3 comments Opened Mar 26, 2026 by eylonisraely Closed Mar 30, 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?
launch Claude Code from a Windows mapped network drive (Z: → UNC path), every Bash call fails with
"Working directory no longer exists" despite the drive being fully accessible to Read/Glob/Grep tools.
What Should Happen?
Anything. I am unable to work on that drive anymore.
Error Messages/Logs
⎿ Error: Working directory "Z:\ClaudeProjects" no longer exists. Please restart Claude from an existing directory.
Steps to Reproduce
he repro is simple: launch Claude Code from a Windows mapped network drive (Z: → UNC path), every Bash call fails with
"Working directory no longer exists" despite the drive being fully accessible to Read/Glob/Grep tools.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
v2.1.84
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗