HTTP/2 makes Cursor unusable

Hey, thanks for the report. This is a known issue on some networks with HTTP/2.

What you can do now:

To help us dig deeper, please share:

  • Screenshot of Settings → Network → Run Diagnostics
  • Network type: VPN/proxy/corporate network, whether Zscaler/Cloudflare/TLS-intercept is present
  • Behavior on another network without VPN/proxy
  • Console errors from Help → Toggle Developer Tools
  • New Request IDs from failed requests

Docs for common issues: Common Issues | Cursor Docs

Let me know if keeping HTTP/2 disabled is stable. I’ll forward the case to the team once I have these details.