Since today, cursor has issues with its “Codebase Indexing”. One step forward, and one back, huh?
Maybe you should consider test driven development
use agent mode, and get a not yet indexed message
Realize even after Reload Window that syncing is stuck at x%
Syncing works, just as before
Windows 10/11
Version: 1.2.2 (user setup)
Remote Access WSL: Ubuntu
I’m not gonna pay more, because indexing doesn’t work
Consider using test driven development, because issues in the IDE happen a bit too often…
Yes - Cursor is unusable
13 Likes
Same here. Indexing is extremely slow, even for small codebases. Not sure if it’ll ever finish at this rate.
Update: It’s been an hour and it hasn’t even reached 10%. I’ve switched to Claude Code for now.
2 Likes
Yeah same for me, it’s being very slow. It seems that version 1.2 new indexing improvement are forcing all previous codebases to re-index.
Honestly, if this brings huge improvements as seen in the https://changelog.cursor.com/ I don’t mind at all waiting an hour for my project to index.
1 Like
Same for me too.
Version: 1.2.2
2 Likes
We are having the same issue, just updated to the newest version of Cursor:
Version: 1.2.2 (Universal)
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:07:27.002Z (1 day ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
1 Like
yeah not a huge fan, that would mean every repository with a larger history is just forced into sitting idly by for a feature they didn’t really ask for. I get that it COULD improve agent performance, but i’m more concerned about a bloated context window at that point(which with the new pricing model can turn into a huge cost issue). and the prompt history for those PRs/commits doesn’t exist either, which means that the llm has to guess what happened and i doubt it will do a good job about it… IF I understand all of that correctly
3 Likes
Yeah you’re right. It’s been almost an hour of codebase indexing and it’s still at 2.9%
This is becoming a showstopper for me. Not sure if indexing will even finish.
1 Like
same here. Just created a new project with a few files and stuck on 30%. If reset cursor, start at 0% over and over again
1 Like
cocode
July 8, 2025, 11:12am
11
It is indexing files which I have removed
1 Like
sjnims
July 8, 2025, 11:46am
12
Same here, stuck at 17.3% for over an hour…
Version: 1.2.2 (Universal)
1 Like
Heelc
July 8, 2025, 11:54am
15
I’m also stuck with codebase indexing.
same here
Version: 1.2.2
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:08:52.104Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
mhaas
July 8, 2025, 12:08pm
17
Same here. Also on Version: 1.2.2, Commit faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0, on arm MacBook
1 Like
mhaas
July 8, 2025, 12:12pm
18
I found a quick fix for everybody looking, you can download an older version of Cursor now (1.1) on their website, and downgrade for now to fix it
2 Likes
nice thanks@cursor-team maybe consider puttign stuff like that on the beta branch so people can test and catch those issues, because it happens a lot lately
It seemed to have improved a few minutes ago, jumping from 15% to 45% in a few minutes, but it’s back to being unusably slow again now.
Downgrading to 1.1 didn’t improve it for me either.
Heelc
July 8, 2025, 1:11pm
21
I feel that there’s an issue with Cursor’s embedding model service, and downgrading to 1.1 didn’t improve the situation
Downgrading didn’t work for me.
, and even after deleting the index and restarting the indexing the same file names appear on the list.
