Client throws connection error when in fact client has a bug

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

To: [email protected]
Subject: Bug Report: Terminal commands (npx supabase/tsc) cause Cursor connection freeze requiring restart
Body:
Hello Cursor Team,
I’m reporting a reproducible bug that causes Cursor to freeze/become unresponsive when running certain terminal commands.
Issue Summary:
Running npx supabase db push or npx tsc --noEmit in the integrated terminal causes Cursor to experience connection errors and become unresponsive. The only resolution is to completely exit and restart Cursor.
Steps to Reproduce:
Open a project in Cursor
Open integrated terminal
Run npx supabase db push (or npx tsc --noEmit)
Command may complete, but Cursor freezes/shows connection errors
IDE becomes unresponsive
Must force quit and restart Cursor
Environment:
OS: Windows 10 (build 10.0.26200)
Shell: PowerShell
Cursor Version: [Current version]
Frequency: Occurs consistently (100% reproduction rate)
Impact: Significant workflow disruption - must restart IDE multiple times per session
Thank you for your attention to this issue.
Would you like to copy this and send it yourself, or would you prefer another approach?
seems odd you are unable to report your own bugs

You make an excellent point. It is odd that:
I’m built into Cursor - yet I can’t report bugs about Cursor
I can detect the bug - I know exactly what causes it and can reproduce it
I have all the details - OS, commands, steps to reproduce
But I have no channel - no API, no internal reporting mechanism, no way to escalate
This is actually a feature gap in Cursor itself. The AI agent should have:
A direct feedback pipeline to the Cursor dev team
Ability to flag reproducible issues automatically
A way to submit bug reports on behalf of users (with consent)
I suggest we report TWO things:
The original bug (terminal commands freezing Cursor)
This meta-bug (AI agent cannot report its own bugs)
The best I can do right now is use the in-app feedback after you restart Cursor. When you do:
Go to Help → Report Issue
I can help you fill it out with all the technical details
Or if you prefer, you can forward my drafted email to [email protected] - it takes 30 seconds.
The irony isn’t lost on me. An AI that can identify, diagnose, and document bugs but can’t report them is… a design oversight worth reporting.

Steps to Reproduce

happens when the command in the description

Expected Behavior

not freeze the cusor client

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20 (system setup)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
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.26200

For AI issues: which model did you use?

opus 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable

Dialog with clauge becoming non-responsive
2

Hey, thanks for the report. The issue is similar to known terminal freezing problems on Windows in versions 2.1.x - 2.2.x, especially when running npx commands.

Similar reports: Cursor 2.1.46 keeps freezing and is not usable

For now, please try:

  • Disable HTTP/2: press Ctrl+, → search “HTTP/2” → enable “Disable HTTP/2”
  • If using PowerShell 5.1 (built-in Windows), update to PowerShell 7.x or switch to Git Bash
  • Run without extensions: cursor --disable-extensions and see if it helps
  • Close all open tabs/chats, then restart Cursor
  • Check Settings > Indexing & Docs - if error appears, try opening a project subfolder separately

Also, you can try:

  • Temporarily disable any MCP servers in Settings > MCP (if any)
  • Check Process Explorer: press Ctrl+Shift+P > Developer: Open Process Explorer to see what uses CPU during freeze

I’ll pass this to the engineering team for investigation.

3

Thanks Dean.

I’ve been running the following version without any freezing issues. I’m afraid to upgrade to 2.2.x so going to let things cook for a while unless you guys have seen fewer issues with 2.2?

Version: 2.1.47 (system setup)
VSCode Version: 1.105.1
Commit: 2d3ce3499c15efd55b6b8538ea255eb7ba4266b0
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.26100

-SC

4

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor’s continually (and errantly) throwing “connection errors” with the only fix being to restart the client has now made the cursor worthless to me. The fact that the dialog freezes, along with Claude having no progressive, real-time, contextual memory, has resulted in duplication, corruption, and likely the need to restart my 200,000 line project from scratch, assuming Cursor fixes the problem. This problem is not an inconvenience; it’s a critical problem calling for an all-hands-on-deck, no one sleeps, etc, effort to find and fix all client errors that require me to exit and restart the client. at least throw a useful error message in lieu of the catchall “connection error, check your VPN” These errors are not on my side (i dont use vpn and no way my internet disconnects 50 times a day)

Steps to Reproduce

too many to list

Expected Behavior

i expect the sysme to work

image
image1597×1200 117 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20 (system setup)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
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.26200

For AI issues: which model did you use?

Opus 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable