So I installed Cursor on my personal Mac (previously Cursor has been only on the corporate Windows computer), ran it and asked Cursor itself what’s wrong with them.
Here’s what it replied:
“Based on my research of common Cursor connectivity issues, here are the main reasons why Cursor might work on your Mac but not on Windows, along with potential solutions:
HTTP/2 Protocol Issues
Some corporate networks, VPNs, or proxies block HTTP/2 which Cursor uses by default
Solution: Try disabling HTTP/2 in Cursor settings:
Open Cursor settings (Ctrl/Cmd + ,)
Search for “http2”
Enable the setting “cursor.general.disableHttp2”: true”
disable http/2 bring the chat back, but I experience index failure issue and in my output I get self-signed certificate in certificate chain, handshake failed error all the time, and the agent basically doesn’t work…
Sorry, I don’t know how to help with the rest of your issues. Maybe try removing all the cache and reinstalling Cursor - that’s what I did (multiple times in different variations) before coming to the solution with http2.
This has been happening much more frequently for me in the past week. I have already had http2 disabled for a couple of weeks. It seems it happens when a single chat gets too long much faster now.
Same issue: 3a108be7-230e-431a-a5d5-4b3e2706f568
I played with http2, restarted pc. This seems to happen after 25 calls and I have to resume the conversation. Please fix ASAP!
I agree… also they don’t fix the problems and won’t reply to request that they can’t be bothered to fix. I guess attracting more easy user is easier than fixing robustness problems for pro users.