Yeah we are experiencing the same issue also
here too, at least not because my internet is so slow in indonesia…
Unfortunately, I am experiencing the same issue here.
Same here: these are my output logs for “indexing and retrieval”:
2024-10-08 10:27:23.073 [error] Handshake failed:
2024-10-08 10:27:23.073 [error] Error: timeout in handshake with retry
at t.RepoClientMultiplexer.handshakeWithRetry (c:…\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:826553)
at async w.getServerStatus (c:…Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:841881)
at async w.startIndexingRepository (c:…\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:844181)
2024-10-08 10:27:23.074 [error] Handshake failed.
2024-10-08 10:27:23.074 [info] Indexing job successfully done or aborted.
still having same issue, last 4-5 days hitting same handshake issue
1 Like
Seriously last 4-5 days. Yesterday only I subscribed for pro and now I regret.
They need to fix this… can’t work with it rn like before
Same here
same issue, pro account!
Version: 0.41.3
VSCode Version: 1.91.1
Commit: 51c8aff7cb5a89f4a0e462fbacab938bdbfaf140
Date: 2024-09-25T17:13:50.377Z
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.19045
Report the same issue, day-1 free user. On chat window: “Codebase chat is falling back to BM25, which is slower and less accurate than embeddings.”
When clicking “Open Settings” > “Retry Index”, I saw it’s running and eventually showed “Handshake failed.”
same issue here, handshake failed last 2 days.
same here… please fix it ASAP, I’m switching to Zed in the interim as Cursor is pointless without the ai being fully operational.
Code indexing loading indefinitely (for an hour straight and nothing happens).
This is a daily thing now. I’m moving out as well, only sticking around until my credits are done since I paid with them. But this is absolutely unusable.
It is great when it works… but those “working” windows are becoming increasingly small.
Happening here as well, not to pile on…
1 Like
Experiencing this issue as well on a pro account.
Same here, unusable.
8 hours with this error. Please Cursor, respond!!!
1 Like
8? more…
Same here