@yumaheymans thanks for the update and appreciate you trying things out. My goal is to find the cause and get Cursor working again for you.
As its not something we can reproduce based on current information, it may be necessary to try more out and perhaps even reset Cursor settings or reinstall it if the issue persists.
Options to try first in this order:
From your video recording it points at at either large Cursor DB or extension storage, could you have a look at ~/Library/Application Support/Cursor and see if there are any unusually large files or folders (GB range). This could point out if any extension is using resources or the database.
Command Palette: Developer: Open Logs Folder and have a look there if any errors show.
Create a new empty project with your settings unchanged to see if that helps.
Check Developer Tools > Console logs for errors, as it might point towards issues and post them here.
You can back up your settings folders in case you prefer to restore them.
See on following page the steps Clearing app data and Reinstalling in case clearing app data didn’t help.
any qeird things here?? trying to debug cursor, also check online
Web Search(“cursor editor “No ptyHost heartbeat after 6 seconds” warning 2025”)
⎿ Did 1 search in 29s
The “No ptyHost heartbeat after 6 seconds” warnings you’re seeing are a known issue with
Cursor editor. Based on the search results, this is a widespread problem affecting many
users across different operating systems.
What’s happening:
The ptyHost (pseudo-terminal host) is the component that manages terminal functionality
in Cursor
It’s losing connection/heartbeat every 6 seconds, causing terminal freezes
This is not related to your code or system configuration - it’s a Cursor editor bug
Key findings:
Persistent issue: Has been affecting users for months as of 2025
Cross-platform: Affects Linux, Windows, and macOS users
Version-independent: Occurs across multiple Cursor versions (0.50.4, 1.0.0, etc.)
Terminal-specific: Integrated terminal becomes unusable, freezing every 6 seconds
VS Code works fine: Same systems run VS Code without issues
Impact on your workflow:
Terminal functionality may be unreliable
You might experience freezes when using integrated terminal
The warnings themselves are harmless but indicate underlying terminal issues
Workarounds:
Use external terminal instead of Cursor’s integrated terminal
Consider switching to VS Code temporarily if terminal usage is critical
Monitor Cursor’s GitHub issues and community forum for updates
This is definitely a Cursor editor issue, not something wrong with your system or code.
what is the issue exactly and what issues is it casuing
What is the ptyHost issue exactly?
ptyHost is Cursor’s pseudo-terminal host - the background process that manages all
terminal functionality in the editor. The “No ptyHost heartbeat after 6 seconds” warning
means:
Heartbeat mechanism: Cursor expects ptyHost to send a “heartbeat” signal every few
seconds to confirm it’s alive and responsive
Connection failure: When no heartbeat is received for 6+ seconds, Cursor assumes
ptyHost has crashed or become unresponsive
Process management issue: The ptyHost process is either:
- Freezing/hanging
- Crashing silently
- Getting stuck in system calls
- Having communication issues with the main Cursor process
Specific issues this causes:
Terminal freezes
Integrated terminal becomes completely unresponsive for 6+ seconds
Commands hang mid-execution
Can’t type or interact with terminal during freezes
Command execution problems
Long-running commands (like npm install, builds, tests) get interrupted
Git operations through terminal may fail
Development server commands become unreliable
Extension and feature impacts
Any extension relying on terminal functionality breaks
Built-in features like debugging, task running affected
Shell integration features stop working
Performance degradation
Cursor may become sluggish overall
CPU usage spikes as it tries to restart ptyHost
Memory leaks from repeatedly spawning terminal processes
Development workflow disruption
Can’t reliably run development commands
Testing workflows become frustrating
Forces developers to use external terminals
Technical root cause:
The issue appears to be in Cursor’s terminal process management - specifically how it
handles:
Process lifecycle management
Inter-process communication between main app and terminal
System resource allocation for terminal processes
Recovery mechanisms when terminal processes fail
This is a core infrastructure problem in Cursor, not a surface-level bug, which explains
why it affects so many users across different platforms and persists across versions.
still getting this though, sometimes chat is not initiating the request, happens like every 5 requests, after a minute of two waiting sometimes resolves
Request ID: 379bd5fc-6711-4849-9f7e-3551eccaf59f
ConnectError: [unknown] Connection failed.
at lJ.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Volumes/Cursor%20Installer/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2565:24471)
at async si (vscode-file://vscode-app/Volumes/Cursor%20Installer/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4516:24730)
Alongside the ‘Connection Failed’ error, that request ID is not logged within our system, which does suggest some kind of networking issue that is preventing Cursor from talking to it’s servers.
Can you try going to the Cursor Settings → Network and run a Diagnostic test?
Also, try switching to HTTP1.1, which is a more compatible but slightly slower networking option.
Web Search(“cursor editor “No ptyHost heartbeat after 6 seconds” warning 2025”)
Stuck in 30 mins with Gemini-2.5