When I open the Cloud Agents tab in Cursor Settings within the IDE, it doesn’t recognize the git repository and bars me from doing any sort of configuration for that. This happens in the WSL version of the IDE. As a workaround I have to like to open the repo in windows version to configure the environment. This isn’t a major issue right now, but a inconvenience to open the same folder in native windows to make changes to the cloud environment snapshot. Would be nice to fix this.
Btw this issue is inconsistent. Sometimes it shows up, sometimes it doesn’t. Also, I remember this being an issue since the beginning *during the beta of background agents) with WSL, so not sure why this hasn’t been permanently fixed once and for all lol.
Steps to Reproduce
Open any git repository using wsl using the cursor . command in the WSL terminal.
Expected Behavior
Should show the configuration settings for cloud agents in WSL.
Hey, thanks for the report. A similar issue happened before and I think it got fixed in an update (see Background agents + WSL cannot be configured), but it looks like it’s back.
To help us debug, can you share:
What Git version are you using in WSL? git --version
How often does this happen, every time you open it or only sometimes?
If you open Developer Tools (Help > Toggle Developer Tools), do you see any errors in the console when you open the Cloud Agents settings?
For now, the workaround is to open Cursor natively on Windows to configure it, like you’re doing. But we’d like to understand the pattern so we can pass it to the team for a permanent fix.
I think it’s sometimes, coz yesterday I had configured the environment for a repo directly without doing the native windows switch. So, I think its intermittent. Today I can’t get it to work though.
So, I opened the dev tools, cleared the console and then opened the cursor settings and got this (consistently whenever I open cursor settings) workbench.desktop.main.js:34103 Error checking repo readiness: Error: spawn /usr/bin/git ENOENT
Thanks for the info. Yeah, this is a known issue with WSL path resolution. Cursor tries to use Windows path separators (\) instead of Linux (/) when running in WSL, which leads to spawn /usr/bin/git ENOENT.
Can you try updating to the latest version (Help > Check for Updates)? The latest version is 2.4.26.
If the issue still reproduces on the latest version, let me know. I’ll create a ticket for the team. It would be either a regression or an incomplete fix. In your reply, please include:
Your version after updating
Whether it reproduces consistently or intermittently (you mentioned it sometimes works)
it says no updates available when I click on “Check for Updates”
Edit: Nvm, switched to Early Access under Beta to upgrade to 2.4.26 and the issue persists in this version as well with the same message in console. Not sure about intermittence right now, but generally that sometimes is very rare when it works. Almost most of the time it doesnt work in WSL
I’m facing the exact same issue as described above. Even with a fresh Laravel Sail setup on WSL (Ubuntu), Cloud Agents insist that there is no Git repository, while the terminal and the source control tab work perfectly.
Direct WSL Path: I am opened via \\wsl.localhost\Ubuntu\home\fatih\dev\wd-psyprax-nexus
Manual Git works: I can commit and push via terminal and Cursor’s UI without issues
Safe Directory: Added the path to safe.directory in global git config — no change
Toplevel Check:git rev-parse --show-toplevel correctly returns the project root
Indexing: Tried “Resync Index” and “Delete Index” multiple times.
Observations: The “Open Folder” button in the Cloud Agents settings page seems to ignore the fact that the folder is already open and valid. It seems like the Agent-subsystem is looking for a Windows-native Git path or fails to communicate with the WSL-Git-bridge.
As mentioned by others, it only works if the repo is cloned directly onto the C: drive, which is not a viable workflow for WSL/Docker development.
