Is Cursor 2.0+ laggy as hell for anyone else?

Discussions
1

Ever since the 2.x updates (currently on 2.3), the experience has gone downhill fast. Please tell me I’m not the only one.

The wildest part? Scrolling through a basic markdown file feels like dragging a boulder. Not AI features, not autocomplete — just scrolling. The lag is painfully obvious.

The exact same file in VS Code? Butter smooth. In Cursor? Feels like wading through mud.

3

Starting from about 10 hour - version 2.3.34 - My cursor terminal when using claude is very laggy and showing API / Internet problem. :frowning:

4

Hey, thanks for the report. Need a bit more info to figure this out:

  1. What’s your Cursor version? (Help > About Cursor > Copy)
  2. OS?
  3. Any installed extensions? Try running Cursor with cursor --disable-extensions from the command line - does the lag persist?
  4. Size of the markdown file that’s lagging?
  5. Open Process Explorer (CMD/CTRL + Shift + P > Developer: Open Process Explorer) - which processes are eating CPU when scrolling?

Also try:

  • Settings > Application > Experimental > Extension Monitor Enabled, then CMD/CTRL + Shift + P > Developer: Open Extension Monitor - maybe an extension is slowing things down
  • Cursor Settings > Network > Run Diagnostics - share the results

@Kamil_Sierocki Hey, can you share the Network Diagnostics results (Cursor Settings > Network > Run Diagnostics)?

5

It is laggy for me only when I have a long chat open so I usually dont go beyond 3 messages in a single chat.

1 Like
6

Environment

  • Cursor: 2.3.34 (system setup)
  • VS Code: 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: Windows_NT x64 10.0.19045

This issue occurs while using Claude Code from the WSL terminal (CLI). I am not using Cursor Chat.

When the session becomes long or the task is more complex, Claude Code starts lagging heavily and then attempts to reconnect multiple times (up to 10 attempts). This is the second time today I’ve encountered this behavior.

After restarting Cursor, the issue temporarily disappeared. After resuming the same Claude Code session in the WSL terminal, it continued for a short time, but then got stuck again with:

“Request timed out. Check your internet connection and proxy settings. Retrying in 13 seconds… (attempt 9/10)”

After that, it ends up in:
“API Error: Connection error. ✻ Baked for 14m 17s”

Process Explorer snapshot (sanitized)
Process Name CPU (%) Memory (MB) PID
cursor main 1 208 [PID_REDACTED]
fileWatcher [1] 0 111 [PID_REDACTED]
shared-process 0 129 [PID_REDACTED]
crashpad-handler 0 36 [PID_REDACTED]
extensionHost [1] 0 340 [PID_REDACTED]
window [1] (Cursor Settings - [PROJECT_REDACTED] - Cursor) 1 526 [PID_REDACTED]
utility-network-service 0 53 [PID_REDACTED]
window [3] (Process Explorer) 0 125 [PID_REDACTED]
gpu-process 0 121 [PID_REDACTED]
ptyHost 0 130 [PID_REDACTED]

Additional notes
At the same time, the logs suggest that connectivity is OK (e.g., successful 200 responses and ping/stream checks).

8

It looks like a network issue during long Claude Code sessions. Try this:

  1. Enable Disable HTTP/2: App Settings CTRL + , > search for “HTTP/2” > check the box. Restart Cursor.
  2. If you’re on a corporate network or VPN, try without the VPN.

Temporary workaround: restart Cursor or split big tasks into shorter sessions.

9

We’re experiencing high demand for Claude 4.5 Opus right now. Please switch to the ‘auto’ model, another model, or try again in a few moments
Again?