@deanrie Hey Dean, is there any update about the topic? Could the team reproduce the issue? Is there any stable work around or a good solution? I would like to continue my project. Thank you!
tried all of this, but it doesnt help at all. Even tried full deinstallation, dont know what to do and I currently don’t want to pay for subscrition for now working app
ctrl + , and there opens settings. search for http2 and disable
@Kyle_Nguyen, the setting got renamed. It’s now Http Compatibility Mode. Pick HTTP/1.1, then restart Cursor.
@Tony2, for your case: the bug is logged and the team is aware. Sadly, there’s no specific fix timeline yet. As a workaround for now:
- Try the latest Cursor version. There have been lots of updates since February, so there’s a chance the behavior changed.
- If that doesn’t help, roll back to 2.2.20 like @xy_hyoga did above. Not ideal, but it will let you keep working.
If the issue still happens on the latest version, share a fresh Request ID. That helps with prioritization.
@KazGroz, your situation is different from the OP. In your March 3 diagnostics (version 2.2.44) it clearly says:
Error: HTTP/1.1 SSE responses are being buffered by a proxy in your network environment
That means your corporate network is buffering streaming connections. Cursor uses SSE Server-Sent Events to stream responses, and if a proxy buffers them, the agent won’t receive data in time and will time out. This isn’t a Cursor bug, it’s a network infrastructure limitation.
What you can try:
- Connect through a mobile hotspot to bypass the corporate proxy and test if it works
- If it works on hotspot, that confirms it’s the corporate proxy. Then ask your IT team to stop buffering SSE or streaming for the domains
*.cursor.sh
Let me know how it goes.