Cursor is unusable due to trying to scan ALL file systems

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor is trying to scan all files using the following command:

/usr/share/cursor/resources/app/node_modules/@vscode/ripgrep/bin/rg --files --hidden --no-ignore --no-config --color=never -g "**/*.code-workspace" -g .cursorignore -g "**/.git/config"

I have a 10-disk drive workstation with billions of files, plus several remote filesystems mounted, plus compressed file systems (via FUSE) with basically infinite files, so running something as reckless as that causes:

  • high disk I/O
  • high CPU usage
  • is guaranteed to pretty much never finish.

This happens on:

  • initial Cursor setup (causes it to hang forever with “Loading…”), have to kill the offending process
  • later (on startup and project open), causing all the fans etc. in my machine to spin up
    • this hangs the startup/open process, everything else is not initialized until that process is killed

Whatever this is, it should be (all of the following):

  • only manually triggered / configurable via an option
  • not cross filesystem boundaries (every self-respecting Unix tool has this option)
  • not follow symlinks

Steps to Reproduce

  1. Have lots of files.
  2. Start Cursor.

This reproduces on a clean setup with no configuration and no extensions.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.43
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: Linux x64 6.17.9+deb14-amd64

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report.

This is a known issue. The team is aware of ripgrep’s scanning behavior on launch, which can impact systems with large filesystems or remote mounts.

Your setup (a workstation with 10+ disks and remote/FUSE mounts) is especially affected. The team is currently reviewing this and working on a fix.

I’ll link this report to the existing issue so it gets visibility.