Describe the Bug
When configuring Cursor to use my WSL‑hosted SSH config:
“cursor.remote.SSH.configFile” : “\\wsl$\Ubuntu\home\username\.ssh\config”)
The connection initially shows the correct host but then fails during install with:
<< ssh: Could not resolve hostname host-alias: No such host is known.
Error installing server: Failed to install the Cursor Server. >>
It appears the extension only uses my custom cursor.remote.SSH.configFile to populate the host list in the menu. When it actually spawns ssh.exe to connect, it ignores that setting and falls back to the default Windows %USERPROFILE%.ssh\config. I confirmed this by copying my WSL ~/.ssh/config into the Windows folder, after that the host resolves correctly, but that workaround isn’t acceptable long‑term.
Steps to Reproduce
On Windows 11 Home (Build 26100), install Cursor and the AnySphere Remote‑SSH extension. Set a custom SSH path file, Restart Cursor and choose Connect to Host.
Expected Behavior
Just like VSCode, Cursor should just use my custom config path and connect without issues.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor