Hey, thanks for the report.
This looks like the known TLS issue over HTTP/2. Please try:
- Settings → type “HTTP/2” → enable “Disable HTTP/2” → restart Cursor and test in a new chat
- Settings → Network → Run Diagnostics → send a screenshot
- Are you using a VPN/proxy/corporate network/SSL inspection (e.g., Zscaler)? Test without it or on another network
- Launch without extensions: in a terminal run
cursor --disable-extensionsand test a new chat - Send 2–3 new Request IDs from failed attempts, plus errors from Help → Toggle Developer Tools → Console
Similar cases and a confirmed fix with Disable HTTP/2:
Let me know if disabling HTTP/2 helps. If it does, keep it enabled while we investigate.