For months now, I’ve been running into the following recurring problem in Cursor IDE, and it’s gotten significantly worse recently — to the point where Cursor is almost unusable for me.
While the agent it working in the chat window, it suddenly stops, giving me this error message:
Connection failed. If the problem persists, please check your internet connection or VPN.
This message pops up frequently — sometimes when starting Cursor, sometimes mid-session, and sometimes repeatedly within seconds. Sometimes I just have to type “go on…” and the session continues, other times It pops right up again until I restart Cursor IDE.
I never have such problems when using the Codex extension for Visual Studio Code.
Apparently I’m not the only one experiencing these problems frequently. I just read about it as a side note in an unrelated blog article.
Steps to Reproduce
Just use cursor for a few minutes. Or hours, you never know. This is an intermittent issue. But in the last few days it’s gotten so bad that I barely use Cursor anymore, despite paying for an Ultra Plan :-\
I have the same problem all the time!
Version: 1.7.54 (user setup)
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26200
Hey Thanks for the report. This is a known connection issue with several common causes. Let’s try the following:
Disable HTTP/2 (the most common fix):
Open Cursor Settings (Ctrl + ,)
Search for “HTTP/2”
Enable “Disable HTTP/2”
Restart Cursor
This helps most users on networks with partial HTTP/2 support.
Check MCP servers (if configured):
Cursor has a limit of 80 tools
Disable MCP servers you’re not actively using
Several users reported this fixed intermittent connection failures
Run network diagnostics:
Cursor Settings → Network → Run Diagnostics
This will check connectivity to Cursor’s servers
Check your firewall/antivirus:
Windows may require re‑allowing internet access for the updated app version (1.7.54)
Let me know if disabling HTTP/2 helps. If not, please share the Request ID from the failed connections (shown in the error message) so we can continue the investigation.
thanks for your quick reply. It seems that the MCP tools were the cause of the issue. I disabled all of them except for browser automation, and so far I haven’t seen the error again. I usually don’t need the browser automation tool either. Is there a way to disable that one as well? I assume it consumes some context on each new chat.
Keep showing Connection issue and i can see my network speed and everything about internet is working. See attached screen shot. If are restart cursor IDE then it’s again works for some time.
Steps to Reproduce
provide prompt anything in cursor IDE. After providing 15 to 20 prompts, cursor IDE keep showing Connection Error.
Expected Behavior
Obviously, it must keep connecting does not matter how many i have used the cursor IDE.
I’ve been using Cursor for the past two days without any connection issues, which was unusual since I had experienced frequent problems almost every day in the past few weeks.
Today, I opened a new instance of Cursor (I already had three others open in different workspaces) and submitted a very long prompt — about 200 KB in size (text file, not tokens).
Right after submitting the prompt, multiple issues started occurring:
The chat froze right after “Planning next moves” for over 3 minutes until I aborted it. Retrying didn’t help.
The Network test showed a very high ping (>1000 ms), even though my terminal showed a stable 14 ms ping to cursor.com.
I closed all Cursor instances and restarted the app. Normally this temporarily fixes the issue, but this time it didn’t.
When I used the search feature inside my workspace, many files didn’t appear at all — only a few incomplete results.
Even searching for a specific string returned far fewer matches than expected.
The only way to get Cursor working again was to reinstall it. After reinstalling, everything worked normally again.
Has anyone else experienced similar issues when submitting large prompts or having multiple instances open?
Connection failed. If the problem persists, please check your internet connection or VPN.
