For the past week, using Cursor has been a nightmare—it’s unbearably slow, laggy, and times out constantly, crippling my workflow. As a paying user, this is completely unacceptable. It’s even more frustrating that this critical issue doesn’t appear to be officially recognized or prioritized by the Cursor team.
Hey, thanks for the report. I’ll need a bit more info to troubleshoot:
Required info:
- Cursor version (Help > About Cursor > Copy)
- OS
- What exactly is slow: chat, agent, just typing, scrolling?
- Cursor Settings > Network > Run Diagnostics, please share the results
Diagnostic steps:
-
Process Explorer:
CMD/CTRL + Shift + P> Developer: Open Process Explorer. Which processes are using CPU or memory when the lag starts? -
Extension Monitor: Settings > Application > Experimental > Extension Monitor Enabled, then
CMD/CTRL + Shift + P> Developer: Open Extension Monitor. Maybe an extension is putting load on the system? -
Quick test: Try running
cursor --disable-extensionsfrom the terminal. Do the lags still happen?
Let me know what you find from these checks and it’ll be clearer what’s slowing things down.
had the same today, especially with gemini 3 pro
what worked was manually hitting /summerize
then it was speedy again
though it really started slowing down just before i hit the new 1000 tool call limit (which is dope conisdering it was 20 something some eons ago ^^)
Hi, Thanks For your help.
my Agent is running extremely slow.
In Auto mode, normally when I ask it to write code based on my keywords, it should start thinking and then begin coding. But now it gets stuck at the “planning next moves” stage. After a long wait, it times out and shows a “VPN xxx…” error message. This is significantly reducing our development efficiency.
The issue is not hardware lag, but a slow and unresponsive Agent. Specifically in Auto mode, it gets stuck at “planning next moves” and eventually times out (often with a VPN-related error message). This is severely hindering development productivity.
Version: 2.3.40 (system setup)
VSCode Version: 1.105.1
Commit: 230922a103262db3487b753c8d1e0a7111c2d780
Date: 2026-01-16T04:42:17.525Z
Electron: 37.7.0Chromium: 138.0.7204.251
Node.js: 22.20.0V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045
Hey, the VPN error when it’s stuck on “planning next moves” is usually caused by a few things. I’ll need a bit more info to pinpoint it:
Really important to check:
- Is Git installed? Go to Cursor Settings > Network > Run Diagnostics and share a screenshot of the results.
- Are you using a VPN or a corporate network?
- What’s the exact text of the “VPN xxx…” error?
Try these workarounds:
-
Disable HTTP/2 (often fixes VPN-related timeouts):
- Open
settings.json(Ctrl+Shift+P> “Preferences: Open User Settings JSON”) - Add:
"cursor.general.disableHttp2": true - Restart Cursor
- Open
-
If Git isn’t installed, the Agent can’t run:
- Download Redirecting…
- During install, select “Add Git to PATH”
- Fully restart Cursor
- Check in cmd:
git --version
-
Check older chats. Do they work? If yes, it might be an indexing issue:
- Cursor Settings > Indexing & Docs
- Try temporarily disabling “Index New Folders” and “Index Repositories for Instant Grep”
-
If you’re on VPN, try turning it off just for a quick test
Similar issues are discussed here:
Share the diagnostics results and tell me if any workaround helped.
It’s almost impossible to use the cursor, and it feels like the IDE is completely useless. The experience is vastly different from what I had in 2025
To pinpoint the issue, I need some diagnostic info from your previous message:
- Network Diagnostics: Cursor Settings > Network > Run Diagnostics, please share a screenshot of the results
- Request ID: When the Agent gets stuck, copy the Request ID (chat menu top-right > Copy Request ID)
- Git: In cmd, run
git --version - HTTP/2: Check your
settings.jsonfor"cursor.general.disableHttp2": true
Also try this:
Switch the model: Gemini 3 Flash may work worse over a VPN
- Try Claude 4.5 Sonnet or GPT-5
- See if it’s faster
Simplify the task: If the Agent is analyzing large logs
- Share a smaller amount of data
- Or make your question more specific so the Agent doesn’t do a full analysis
Without diagnostic info, it’s hard to tell the exact cause. It could be your VPN, the model, or the amount of data.
