Agent command execution uses WSL instead of the Windows default integrated terminal (Git Bash)

Support Bug Reports
, , ,
8

Thanks for the update. useWslProfiles: false only hides auto-detected WSL profiles, but if C:\Windows\System32\bash.exe is available in PATH or there’s some other bash source, the agent detector can still pick it up. Let’s try explicitly limiting the profiles to just Git Bash.

Add this to settings.json (User Settings):

"terminal.integrated.useWslProfiles": false,
"terminal.integrated.defaultProfile.windows": "Git Bash",
"terminal.integrated.profiles.windows": {
    "Git Bash": {
        "path": "C:\\Program Files\\Git\\bin\\bash.exe",
        "args": []
    },
    "PowerShell": null,
    "Command Prompt": null,
    "Ubuntu (WSL)": null,
    "Debian (WSL)": null
}

Adjust the path to bash.exe if Git isn’t installed in C:\Program Files\Git. The WSL distro names in the null block should match yours. You can check what’s visible in Terminal → Select Default Profile in Cursor.

After that, fully restart Cursor (quit the app, not Reload Window) and run the same probe script. uname -a should show MINGW64_NT-..., not microsoft-standard-WSL2.

A couple more notes:

  • You’re on Cursor 3.0.16. The current stable is newer, so it’s worth updating and testing again since there were shell detector fixes.
  • If WSL still starts after the config above, paste your full terminal.integrated.* block from settings.json and I’ll take a look.

This bug is known, no ETA for a fix yet.