Cursor 2.3.34 cannot work on Mac

[Yankai_W]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After upgrading cursor version from 1.7x to 2.3x, my cursor IDE cannot work anymore.

• Cursor version
  Version: 2.3.34
  VSCode Version: 1.105.1
  Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
  Date: 2026-01-10T21:17:10.428Z
  Electron: 37.7.0
  Chromium: 138.0.7204.251
  Node.js: 22.20.0
  V8: 13.8.258.32-electron.0
  OS: Darwin arm64 24.6.0
• Issues
  1. Extension host terminated unexpectedly 3 times within the last 5 minutes.
  2. When asking anything in AI pane, it got stuck in Planning next moves.
  3. Network Diagnostics running got stuck in DNS, HTTP/2 and SSL, never finished.

Steps to Reproduce

1. Every time you open cursor.
2. Every time you ask anything in AI pane.
3. Every time you run Network Diagostics.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Yes - Cursor is unusable

[TheScrappper (Mehmet)]

Same on the windows

Agent chats not opening after update – constant ConnectError: [unauthenticated] and full_stripe_profile 401 errors

Where does the bug appear (feature/product)? Cursor IDE Describe the Bug Describe the Bug, Steps to Reproduce, Expected Behavior. Şu metinleri direkt kopyalayabilirsin. Describe the Bug After the latest Cursor update, I can see my existing Agent chats in the sidebar, but when I click on them they never open or load. In the Developer Tools console I continuously get errors such as: ConnectError: [unauthenticated] Error Repeated requests to https://api2.cursor.sh/auth/full_stripe_profile ret…

[deanrie]

Hey, this is a known issue in version 2.3.34, and the team is already working on a fix. Try this workaround:

1. Open Cursor Settings CMD + ,
2. Search for “HTTP/2”
3. Turn on “Disable HTTP/2”
4. Restart Cursor

This should fix all three issues: extension host, agent, and network diagnostics. Another user with the exact same errors confirmed that switching to HTTP/1.1 helped: Connection Error after upgrade to Cursor 2.3.34

If everything works after that, let me know. If it still doesn’t, please share a screenshot of your settings and the Network Diagnostics results after the change.

[Yankai_W]

Thanks, Dean, but it doesn’t work at all, I remember that these issues happened after 2.x, that was also why I kept using 1.7x before.