Codebase Indexing - Handshake failed

[will-gendron]

Unable to index my codebase all of a sudden. Anyone else experiencing this issue?

[holowolfdan]

same issue here. cant index my code.

[nw303]

yes, me too

[arnavw96]

Same here

[Sam-Forum]

[h4rumon]

Same. Can’t index at all. Handshake failed.
Version: 0.41.3

2024-10-08 16:25:36.850 [error] Handshake failed:
2024-10-08 16:25:36.851 [error] Error: timeout in handshake with retry
	at t.RepoClientMultiplexer.handshakeWithRetry (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-retrieval/dist/main.js:2:826553)
	at async w.getServerStatus (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-retrieval/dist/main.js:2:841881)
	at async w.startIndexingRepository (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-retrieval/dist/main.js:2:844181)
2024-10-08 16:25:36.851 [error] Handshake failed.

[SeekBytes-AI]

Same issue

[rickl]

Might be https://turbopuffer.statuspage.io related

[meir23]

Same issue.

[0xgunter]

same issue

[Bluechimp]

Having the same issue as well, handshake failed won’t index

[ghici]

same issue. It’s most probably a service down, but it’s like the second or third day here since it stoped working.

Also, why does it says that the "Embeddings improve your codebase-wide answers. All code is stored locally "
My code is but my embeddings aren’t ? since the service it’s down it sure uses a cloud service to index those right ? or ? thanks

[AAL]

same and i wasted 500+ fast requests trying to make things work when this was the problem. cursor is useless without indexing.

[rahat1795]

will the answers still be less accurate if i only provide 3 or files as context and the answer doesn’t need the context of the whole codebase?

[AAL]

it’s unusable

[NunoMoura]

I’m having the same “Handshake failed” issue. Are there any updates from the Cursor Team on this?

[s44002]

Same Issues here, team cursor, what the heck is this…

[fcspcs]

worked now for me

[jameso]

Same, unusable for hours…

---

[calderson]

Has this been fixed?