Codebase Indexing gets stuck in an infinite loop on Loading forever

I’m having problems opening my cursor. When I open the cursor, Codebase Indexing gets stuck in an infinite loop on Loading forever, and it doesn’t load my project’s chat and I can’t work.
Anyone else having this bug?
Any idea how to solve it?

Version: 0.47.8 (user setup)
VSCode Version: 1.96.2
Commit: 82ef0f61c01d079d1b7e5ab04d88499d5af500e0
Date: 2025-03-18T05:39:50.993Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.26100

Hey, check what logs are displayed in the Output panel. To do this, go to the View menu -> Output, and in the dropdown menu, select Cursor Indexing & Retrieval.

Also, it might be related to this:

To add to what @deanrie suggested, there are two other possibilities to check that I can think of.

If you’re using custom documentation in Cursor Settings > Features > Docs, be sure you don’t have one stuck or constantly trying to index.

The other culprit could be too large a code base. For instance, if you aren’t using .cursorignore in the root of your project folder and you’re indexing, say, nod_modules, it’ll do nothing but run constantly.

1 Like

I can second Mikes comment. I had before a Docu that was preveting it from working.

Also others reported adding unnecessary folders to .cursorindexignore like node_modules or in some languages the vendor folder.

1 Like