[BUG] [Bug] SSH connection fails on Windows: "Failed to spawn /usr/bin/ssh: spawn /usr/bin/ssh ENOENT"
Open 💬 6 comments Opened Feb 16, 2026 by taylorvalton
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?
Description
The desktop app's "Add SSH connection" feature fails on Windows because it hardcodes the Unix SSH path /usr/bin/ssh instead of using the system PATH to locate the SSH executable.
Error
What Should Happen?
Steps to Reproduce
- Open Claude Code desktop app on Windows
- Add an SSH connection using a host defined in
~/.ssh/config - Attempt to connect
Expected Behavior
The app should locate SSH via the system PATH (e.g., C:\Windows\System32\OpenSSH\ssh.exe) rather than hardcoding /usr/bin/ssh.
Environment
- OS: Windows 11 Pro 10.0.26200
- Claude Code Desktop App Version: v2.1.38
- CLI Version: v2.1.42
- SSH Location:
C:\Windows\System32\OpenSSH\ssh.exe
Workaround
SSH into the remote machine manually and run claude directly from the terminal.
Error Messages/Logs
Steps to Reproduce
Steps to Reproduce
- Open Claude Code desktop app on Windows
- Add an SSH connection using a host defined in
~/.ssh/config - Attempt to connect
Expected Behavior
The app should locate SSH via the system PATH (e.g., C:\Windows\System32\OpenSSH\ssh.exe) rather than hardcoding /usr/bin/ssh.
Environment
- OS: Windows 11 Pro 10.0.26200
- Claude Code Desktop App Version: v2.1.38
- CLI Version: v2.1.42
- SSH Location:
C:\Windows\System32\OpenSSH\ssh.exe
Workaround
SSH into the remote machine manually and run claude directly from the terminal.
Claude Model
Opus
Is this a regression?
No, this never worked
Last Working Version
na
Claude Code Version
1.1.3189
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗