Hello, I’m receiving this message, and I can’t find a way to fix it. I tried a couple of solutions I found on the forum, such as logging out and back into the account or uninstalling and reinstalling Cursor, but nothing worked. Does anyone know what might be going on? Thank you very much.
Same issue here. I’ve created a fresh NextJS project using cursor but code indexing is failing. It is failing even for an empty html project.
There is an ongoing issue with OpenAI’s Embeddings, which is resulting in issues with Codebase Indexes. See here for updates: https://status.cursor.com/
Hello, I see you have a new feature to use non-openai embeddings. Why does the indexing fail with that one too? (Additionally: openai embeddings are working perfectly fine for me again for my own projects - are you sure the error is actually related?)
I’m seeing on status.cursor.com that the codebase indexing issue has been resolved, but I’m still receiving the “Handshake failed” error message.
Update: Codebase indexing is now working again.
I’m still having the same problem, can someone confirm ?
same issue here please solve it account - kinrerrudi@gmail.com
same issue with codebase indexing please solve it - kirnerrudi@gmail.com
17:35 PST, still having the same issue even though the status page says they resolved the issue. Hoping its just taking some time for it to get back up and running for everyone since I see a few comments from people saying its fixed for them.
@jake Is there any comment on this from the cursor team please. I am still seeing “Handshake failed” for all my projects. It’s hard to rely on cursor as a professional tool when it reliably breaks every 3-4 weeks on new releases…
I’ve been advised that the issue is resolved. I’m deleting a project index and retrying it now to confirm.
Edit: is now resolved. Confirming that it’s working on my end as well (previously wasn’t).
Not only the codebase indexing is failing for me, cursor agent also starts hallucinating a lot. Even after providing the exact instructions, in a couple of iterations it starts losing context. Been getting this issue for 2 days. Lost a bunch of fast requests. 
Is anyone else facing something like this?
Hey, the worse performance from the Composer will be due to the first issue of codebase indexing failing. Can you confirm if this is resolved now?
Hey, which version of Cursor are you using?
Unfortunately, Cursor is not working same as before. it is stuck into searching codebase forever. Tried resetting composer sessions, relaunching Cursor, nothing seems to fix it. This is the 3rd day.
It looks like better to stay away from Cursor for a couple of days, until it becomes stable, or all those fast requests will dry up with no productive result.
Hey, can you try renaming the folder your code is stored in, to see if that sorts the indexing out?
Note that this will remove your Composer / Chat history for that codebase.
1 Like
Can confirm, after renaming the folder, it worked on 0.44.11
1 Like
Thanks, that worked. Hopefully it continues.