Scanning folder for Git repositories

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When cloning the repository in Cursor, it gets stuck on “Scanning folder for Git repositories” under the Source Control tab, as shown in the screenshot. The issue persists even after waiting for 30 minutes to an hour. In most cases, a complete reinstallation is required, and even that does not consistently resolve the issue. Can anyone help me with the fix ?

Steps to Reproduce

Sometimes it’s hangs forever

Expected Behavior

Git repositories should be detected and displayed normally
Source Control should become available for regular use.

Screenshots / Screen Recordings

Cursor_issue.png
Cursor_issue.png484×145 4.71 KB

Operating System

Windows 10/11

Version Information

Version: 3.2.16 (system setup)
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Yes - Cursor is unusable

7

This is a known bug with the Git extension’s repository scanning. It has been reported across multiple Cursor versions on Windows. A few things you can try:

  1. Change the repository detection mode. Open Settings (Ctrl+,), search for git.autoRepositoryDetection, and set it to openEditors. This skips the directory scan and only detects repos for files you actually open. This is the most effective workaround.

  2. Restart the built-in Git extension. In the Extensions panel, search for @builtin git, click the gear icon on “Git”, choose Disable, then Enable it again, and Reload the window.

  3. Open the project folder directly rather than a parent or higher-level directory.

You can also find more details and discussion in this related thread: Source Control hangs on “Scanning workspace for Git repositories…”

Our team is tracking this for a fix. Let me know if the openEditors setting helps.

8

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The source control in Cursor IDE shows “Scanning for Git repository…” infinitely when the IDE is opened for the first time after system startup
I am having to restart cursor for the source control to recognise my git repository and pull up the current branch and changed files etc.
Issues is when opening for the very first time after system startup it isn’t recognising the git.

Steps to Reproduce

Turn on system → Open Cursor IDE → source control extension

Expected Behavior

Shows the text “Scanning for git repositories…” infinitely

Operating System

Windows 10/11

Version Information

Version: 3.3.16 (user setup)
VSCode Version: 1.105.1
Commit: 7f0f522221d0ba220e4edb766bb3c47c08c14ab0
Date: 2026-05-06T20:40:56.501Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

9

Thank you for your response. I have tried the provided solution, but it didn’t work for me.

10

A couple of follow-up questions to narrow this down:

  1. After changing git.autoRepositoryDetection to openEditors, did you reload the window (Ctrl+Shift+P > Developer: Reload Window)? The setting won’t take effect until the window is reloaded.

  2. Are you opening the project folder itself (the one containing .git), or a parent directory that contains multiple projects?

  3. Does the same project work normally in VS Code (not Cursor)?

  4. Could you check if there’s a rg (ripgrep) process consuming high CPU while the scanning hangs? Open Task Manager (Ctrl+Shift+Esc), look for rg.exe or ripgrep, and note what path it’s scanning.