Windows: Backslashes stripped from paths causing 'No such file or directory' errors

Resolved 💬 3 comments Opened Jan 31, 2026 by richiestanaway Closed Feb 3, 2026

Description

On Windows with Git Bash, Claude Code internally generates paths with backslashes that get stripped when passed to bash commands, causing errors like:

Error: Exit code 1
/usr/bin/bash: line 1: cd: C:Usersrichidvisecloudfish-speech: No such file or directory

The path C:\Users\richi\dvise\cloud\fish-speech becomes C:Usersrichidvisecloudfish-speech (all backslashes removed).

Environment

  • OS: Windows 11
  • Shell: Git Bash (/usr/bin/bash)
  • Claude Code version: Latest

Steps to Reproduce

  1. Run Claude Code on Windows with Git Bash as the shell
  2. Have Claude Code attempt to run bash commands that involve changing directories or referencing Windows paths
  3. Paths with backslashes get mangled

Expected Behavior

Paths should be properly escaped or converted to forward slashes before being passed to bash.

Workaround

Using forward slashes (C:/Users/...) or Git Bash-style paths (/c/Users/...) works correctly.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗