[BUG] Windows 11: Write tool and Bash tool cannot write files visible to the real file system
Status Closed — not planned
Reported on v2.1.195
Maintainer reply None cached
Activity 2 comments · opened Jun 27, 2026 · closed Aug 13, 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?
Environment:
- OS: Windows 11 Enterprise 10.0.26200
- Claude Code: standalone CLI window (not VS Code terminal, not JetBrains)
- Shell: bash (Git Bash / POSIX sh)
Steps to reproduce:
- Run Claude Code in a standalone CLI window on Windows 11
- Use the Write tool to create a file at D:\folder\test.txt
- Use Bash tool: echo "test" > "D:\folder\test.txt"
- Also tried ! echo "test" > "D:\folder\test.txt" prefix in prompt
What Should Happen?
Expected behavior:
The file should appear in D:\folder in Windows File Explorer.
Error Messages/Logs
Actual behavior:
- Write tool reports success but the file is not visible in File Explorer
- Bash tool commands also cannot create files visible in the real file system
- Files only exist inside the sandbox environment, completely isolated from the real Windows file system
- The ! prefix for direct shell execution also doesn't work in this environment
Steps to Reproduce
Impact:
Claude Code is effectively unusable for any file operations on this Windows setup. Cannot create, edit, or modify any
files in the user's actual working directory.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.195
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗