Errors that are reported as “Connection Error” are not actually connection errors, or they need to have clearer traces. I cannot do anything with “Request ID: 9d8f6f9b-ddb9-44b5-8ac9-f8aee887ecfd”
Steps to Reproduce
It happens sporadically. Sometimes, the conversation has been going on for a long time and at a certain point you can never continue that conversation because it seems to be permanently stuck (how is this a “Connection Error”?)
Sometimes, it happens right away in a new window when you ask it to do certain tasks (it will respond to me if I ask it for a discussion, and claim “Connection Error” when it is exploring my files).
Expected Behavior
I expect to be informed about what is actually happening so that I can stop losing important agent chats unnecessarily, and stop wasting tokens on repeating requests that fail halfway through. Right now I get charged for each partially completed request - and sometimes it’s not a few pennies but dollars that are potentially wasted.
By the way, these “Connection Error” issues also sometimes go away when I hard-close the application and restart it. This further evidences that the issue is not fundamentally about connection errors at the root.
Thank you for the help Dean, but there is no obvious “Disable HTTP/2”, I can only downgrade to HTTP/1.1 or HTTP/1.0 - for now I tried selecting HTTP/1.1 . I hope this works
In case anyone else is looking for the setting, as of 12/31/2025, I found it in File → Preferences → Cursor Preferences, then searched for HTTP and found the “HTTP Compatibility Mode” setting.
I am not running on any special VPNs or Proxies - this is just my personal PC connected to a standard Quantum Fiber WiFi network. That said, Quantum Fiber Q1700k routers are opaque and don’t allow me to really see or configure settings outside of what they push to me through their own updates - entirely possible that is contributing to some of the channel instability, but it’s low probability given that restarting Cursor is commonly a resolution to this error.
what exact commands the agent is trying to run right before the error?
It failed when trying to explore my files, grep, and run commands - seemed like it hiccupped whenever it tried to use a “tool” and was fine when it just had to spit out tokens at me without doing anything extra (I didn’t think of this at the time but I could have tested if it was consistent across all tool calls).
To follow up, I applied both recommended fixes here and haven’t had the Connection Issue since after more than a day of use. Time will tell but the HTTP/2.0 pipeline is looking pretty suspicious right now.
