If remote SSH disconnects and it prompts for the password again, cursor consumes a constant 31% of my GPU making my laptop get very hot. Is it stuck in a tight redraw loop when it should be idle?
Once I enter and submit the password cursor stops burning the planet.
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Hey there!
While the SSH reconnect/password prompt is showing, Cursor sits in a “reconnecting” state and keeps repainting the spinner, which pegs the GPU until you reconnect or dismiss the prompt (that’s why entering the password stops it). We’ve seen this before, and I’ll get it back in front of the team.
A couple of things that help right now:
Dismiss or cancel the reconnect prompt (or just reconnect) as soon as it appears. GPU drops right back to normal.
If it keeps happening and the heat is the main issue, open the Command Palette (Ctrl+Shift+P), run Preferences: Configure Runtime Arguments, set "disable-hardware-acceleration": true, and restart Cursor. That switches to software rendering, so only keep it on while you need it.
One thing that’d help us reproduce: what usually triggers the disconnect for you (laptop sleep/wake, VPN, or a network change)?
I VPN to a datacentre. The drop can be due to VPN drop (rare) or network glitch in the DC, which is more frequent (once every few days) due to the 100G DC network being heavily saturated.
My laptop is permanently on to maintain various connections. If the SSH cursor is using glitches and disconnects then the laptop becomes busy with fans running, possibly unattended and while the screen is locked so could potentially continue to remain in this state for a weekend.
I have attempted to work around this situation by configuring SSH keys.