I am seeing this a lot today, very rarely before. Has the update changed a default setting or something:
Hey, there were incidents with the codebase yesterday. What happens if you click on retry index? Will it also fail?
Hello, I still have that same issue, it does not seem resolved at this time. Manually or automatically trying to index the codebase.
Thank you!
Yes, I retried and it came back (after some itme) with the same handshake failed message
Which version of Cursor are you using?
0.45.1
That’s what I thought. We’ve rolled back to version 0.44.11, and everything works fine in it. You can download this version here:
We will also soon release a new update that fixes many issues.
Hmmm, thanks, I suppose 
Edit 2: It works now. Maybe it was caused by Cursor is down January 24, 2025? - #63 by routingtable
For me, it started today. I was able to get a couple of uses of composer before it happened. I had no problems yesterday.
I am stuck with “Note: codebase not indexed yet. Results are much better when indexed. Currently indexing…”
It does not allow me to use the composer because of that.
Under Cursor Setting / Features, it shows “Setting up indexing…” forever.
Cllicking “Pause Indexing” and “Resume Indexing” didn’t work. It continues to show “Setting up indexing…” forever.
Clicking “Delete Index” and “Confirm” didn’t work. The spinner beside Confirm just spins forever.
Restarting Cursor and computer didn’t help.
Edit: After a few restarts and letting it run “Setting up indexing” for some time, it says “Handshake failed”. But clicking on “Retry Index” just sends it back to “Setting up indexing”.
OS: Ubuntu 22.04.5
Version: cursor-0.44.11-build-250103fqxdt5u9z-x86_64_156399a3096e386a55a7f3a54adcd74c.AppImage