[BUG] The drive letter E: gets mangled into E- in the temp path, producing E--python-source (double dash)

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?

The root cause: The Bash tool writes its output to a temp file at C:\Users\nksal\AppData\Local\Temp\claude\E--python-source\tasks\. Every single attempt fails with EINVAL:
invalid argument when trying to open that file. This is happening inside Claude Code's infrastructure — before any command even runs.

Why: Your working directory is E:\python\source. The drive letter E: gets mangled into E- in the temp path, producing E--python-source (double dash). Something in the file I/O
layer chokes on this path or fails to create the directory structure.

• Platform: Windows 11, PowerShell
• Repo on non-C: drive: E:\python\source
• Error: EINVAL: invalid argument, open 'C:\Users\...\Temp\claude\E--python-source\tasks\*.output'
• Cause: Drive letter E: gets mangled to E- in temp path, Bash tool can't write output files

What Should Happen?

Drive letter E: should work seamlessly

Error Messages/Logs

Steps to Reproduce

• Platform: Windows 11, PowerShell
• Repo on non-C: drive: E:\python\source
• Error: EINVAL: invalid argument, open 'C:\Users\...\Temp\claude\E--python-source\tasks\*.output'
• Cause: Drive letter E: gets mangled to E- in temp path, Bash tool can't write output files

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.56

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_