Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Version control can’t detect the git folder in the main working directory. It is stuck at the “Scanning folder for Git repositories…” message.
Steps to Reproduce
Nothing specific. Open a workspace, and it fails to detect the git folder.
Expected Behavior
Detect the folder and sync local repo.
Screenshots / Screen Recordings
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.2.17
VSCode Version: 1.105.1
Commit: cf858ca030e9c9a99ea444ec6efcbcfc40bfda70
Date: 2025-12-11T18:30:06.649Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.14.0-37-generic
Additional Information
I tried different folders and projects, all failed.
Does this stop you from using Cursor
Yes - Cursor is unusable
user1445
(Yihang Wang)
December 12, 2025, 2:29am
2
Same here, really frustrating, starting using AntiGravity.
Version: 2.2.17
VSCode Version: 1.105.1
Commit: cf858ca030e9c9a99ea444ec6efcbcfc40bfda70
Date: 2025-12-11T18:30:06.649Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0
user1445
(Yihang Wang)
December 12, 2025, 3:35am
3
I revert Cursor to to follow version (2.1.41), the source code functionality starts working.
You can download the older version from GitHub - flyeric0212/cursor-history-links: 自动抓取并维护Cursor各平台(Windows、macOS、Linux)的历史版本下载链接,让用户可以根据需要安装或降级到特定版本。
Version: 2.1.41
VSCode Version: 1.105.1
Commit: 1321aa9140784391e83a406174345e818fe156f0
Date: 2025-11-30T18:58:57.968Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0
2 Likes
deanrie
(Dean Rie)
December 12, 2025, 9:21am
4
Hey, thanks for the report. This looks like a regression in 2.2.17. I’ll escalate the bug to engineering.
Could you help with diagnostics:
View > Output > select Git and share logs from the moment the workspace starts
Help > Toggle Developer Tools > Console and attach errors
Installed git extensions and the result when launching with extensions disabled:
From terminal: cursor --disable-extensions
Does the same repo work in VS Code 1.105.1 on this machine?
Please also check:
Settings > Git: Enabled is on
Settings > Git: Auto Repository Detection is on
Open the folder that contains .git directly, not a higher-level folder
Please send the requested info and screenshots. I’ll update the thread as soon as we have a fix or a build with the patch.
Hey!
I could gather some logs from Developer Tools, but couldn’t find Git Output View.
Tried disabling extensions - no luck
Latest VS Code is working fine with my repo
Version: 1.107.0
Commit: 618725e67565b290ba4da6fe2d29f8fa1d4e3622
Date: 2025-12-10T07:43:47.883Z
Electron: 39.2.3
ElectronBuildId: 12895514
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Linux x64 6.14.0-37-generic
All three checks are done, and they are OK
vscode-app-1765555992924.log.txt (9.7 KB)
Any updates on this? I tried AppImage too but no luck. I con not use Cursor for the last week and will switch if this is not resolved.
user1445
(Yihang Wang)
December 18, 2025, 12:04pm
7
Still not resolved after several patch updates, please.
Version: 2.2.36
VSCode Version: 1.105.1
Commit: 55c9bc11e99cedd1fb93fbb7996abf779c583150
Date: 2025-12-18T06:25:21.733Z (5 hrs ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.3.0
For me, it looks like an rg process triggered by Cursor Remote-SSH (I suspect) that scans my entire $HOME. The issue is that I happened to have a very large remote NFS mounted under $HOME, so the scan got stuck.
The process command looked something like this:
/home/USER_NAME/.cursor-server/bin/20adc1003928b0f1b99305dbaf845656ff81f5d0/node_modules/@vscode/ripgrep/bin/rg --files --hidden --no-ignore --no-config --color=never -g **/*.code-workspace -g .cursorignore -g **/.git/config
My workaround was to unmount that NFS mount point, and voilà—it was fixed.
If anyone from the Cursor team is reading this: I think this rg process should run under the target project/workspace path, not under $HOME.
ravirahman
(Ravi Rahman)
January 9, 2026, 9:26pm
10
Thank you for this bug report; we are looking into it!
c00l
(c00l)
January 22, 2026, 4:19am
11
After today’s update, I can’t use Cursor anymore. Any updates on this issue? What’s going on with your product? I’ve paid for a 1 year subscription and this is what gets released?
jiaqin
(Victor)
January 22, 2026, 4:23pm
13
This is a very serious bug. It has been blocking me from updating Cursor for more than a month! Please fix it ASAP.