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)
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.
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?
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)
