Cursor Wsl2 failed to clone remote rule from github

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

  1. The cursor-retrieval extension in Cursor IDE throws a spawn /usr/bin/git ENOENT error when executing the git clone command, preventing it from automatically cloning the rules repository.
  2. After manually cloning the repository to \root\.cursor\projects\root-Project-fastapi-casbin\rules, Cursor still fails to recognize the rules.

Steps to Reproduce

  1. Connect to WSL2 Ubuntu via Cursor.
  2. In Cursor Settings, add a rule via Remote Rule (GitHub) and enter GitHub - zxjlm/cursor-fastapi-rules.
  3. The error occurs.

Expected Behavior

Rule succeed to add in the project .

Screenshots / Screen Recordings

giterror.png
giterror.png488×178 8.86 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.43 (user setup)
VSCode Version: 1.105.1
Commit: 32cfbe848b35d9eb320980195985450f244b3030
Date: 2025-12-19T06:06:44.644Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

Not use AI

For AI issues: add Request ID with privacy disabled

Not use AI

Additional Information

  • WSL2 Version： 2.6.3.0
  • Linux： Ubuntu 22.04.5 LTS (Jammy Jellyfish)
  • Core： 6.6.87.2-microsoft-standard-WSL2
  • Git Version： 2.34.1

I can manually to clone the repository use git to the local folder. but after manually cloning the repository to \root\.cursor\projects\root-Project-fastapi-casbin\rules, Cursor fails to recognize the rules.

The Cursor settings -> Rules and commands -> Project Commands display nothing.

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

may be it because of the path cursor used .

wrong：


cwd: \root\.cursor\projects\root-Project-fastapi-casbin\rules

right：


cwd: /root/.cursor/projects/root-Project-fastapi-casbin/rules
5

Hey, thanks for the report! You’re absolutely right. The issue is that Cursor uses Windows path separators (\) instead of Linux (/) when running in a WSL2 environment.

This is a known issue with Extensions in WSL. The team is already working on fixing path handling for WSL2.

Unfortunately, there’s no working workaround for Remote Rules in WSL right now. Even manual cloning doesn’t help, because Cursor still uses the wrong path format when trying to detect the rules.

As a temporary workaround, you can use local .cursorrules files instead of Remote Rules.

6

Alright, thank you for your reply. I’ll start by using .cursorrules , and look forward to further resolution.

1 Like
8

I also received that notification. I hope it will be fixed soon :(((