Scanning folder for git repositories is taking forever

Support Bug Reports
, ,
1

When I restart my session on a remote server (due to network disconnection), cursor seems to get stuck at `Scanning folder for git repositories. This also blocks the agent chat window, I get `Agent execution timed out for whatever message I sent out.
I am not sure if these two issues are connected to each other but it is making cursor un-usable.

4

Hey, thanks for the report. These two issues are most likely related. When git scanning hangs, it blocks the extension host, and because of that the agent can’t start and shows “Agent execution timed out”.

Git repository scanning can sometimes get stuck in an infinite loop, especially on remote servers. A similar case is described here: Cursor Git tab hangs due to invasive ripgrep scanning on network/FUSE mounts (Linux).

A few questions to better understand what’s going on:

  1. What OS is running on the remote server (Linux distro and version)?
  2. What Cursor version are you on?
  3. Does the server use NFS, FUSE, or any other network file systems?
  4. Roughly how big is the working directory you’re opening?

As a workaround, please try:

  • After reconnecting, run CMD/CTRL+Shift+P then “Developer: Reload Window”
  • Open the project folder itself, not a higher-level parent folder
  • In Settings, try disabling git with "git.enabled": false (you’ll lose git integration, but the agent should work)

Let me know if any of these workarounds help.

5

Thanks for the reply! I was previously on a login node that may be slow for scanning, so I tried to switch to a GPU node and haven’t seen this issue in the last week, until now it happens again on this GPU node when I am trying to open a new folder.
Here are the answers to your questions:

  1. OS: Ubuntu 22.04.5 LTS (Jammy Jellyfish) Kernel: 6.8.0-1028-aws (AWS-optimized kernel) Architecture: x86_64
  2. Cursor version: 2.4.31
  3. My current workspace is on the Lustre network file system.
  4. Fairly small, only 4.7MB

Follow-up: I tried to update cursor to 2.5.17, close all other connections and re-open any folder that can be connected before, still seeing the same issue!

Again this brings very negative user experience, cursor is basically un-usable in this case and waste a lot of my time (ofc I don’t want to disable git)

Can someone from the team take a more serious look at this issue?

6

My Cursor install is also stuck at “Scanning folder for git repositories…” after updating to 2.5.17. I’m working in a local project folder and the git repo is in the root of the project folder so a super normal setup.

Developer: Reload Window didn’t have any impact.

Version: 2.5.17 (user setup)
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.22621

EDIT: After several cursor restarts and switching between different project folders I finally got mine to load again ¯\_(ツ)_/¯

7

Same here, using WSL but not Windows, since 2.5. Reloading window does not work.

Version: 2.5.17 (system setup)
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100

8

I somehow get around this:

Go to extension, search for @builtin git and restart the basic git extension. Then reload the window, it worked for me after this

2 Likes
10

I solved problem to do this

11

Have the same problem, sometimes forever, sometimes for 5 minutes.

Version: 2.6.12 (user setup)
VSCode Version: 1.105.1
Commit: 1917e900a0c4b0111dc7975777cfff60853059d0
Date: 2026-03-04T21:41:18.914Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200