Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Cursor Agent chat consumes 100% GPU when waiting for confirmation to run the next step. I have set at the prompt for 30 minutes, with no differences. I took a screenshot of my Cursor prompt to show that nothing is going on, other than waiting for confirmation.
I also took a screenshot of my GPU performance to show that it’s spikey …cycling about every 5 seconds …endlessly.
Finally, I “rejected” the proposed action, dropping to a mode where Cursor was waiting for me to type something. At this point, the GPU performance dropped dramatically, effectively going to 0 w/i a few minutes. I also provided a screen shot of the transition between Cursor waiting for a confirmation and Cursor waiting for me to type something.
Steps to Reproduce
There are many, many times that this has happened to me. I keep updating Cursor hoping this goes away …as it eventually always ends up eating my GPU (and therefore useable system) 100%.
Since I’m usually asking Cursor to “do things for me”, I suspect this happens during the Prompt Loop as illustrated here. However, I can’t be certain this is ONLY in the prompt loop as it happens to me all the time.
Expected Behavior
Cursor should NOT be in an “agent” LLM “thinking” mode during awaiting my prompt reply. It should be doing nothing, same as when I say “Reject”.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.5.5 (user setup)
VSCode Version: 1.99.3
Commit: 823f58d4f60b795a6aefb9955933f3a2f0331d70
Date: 2025-08-25T17:40:25.290Z
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.26100
Additional Information
This particular situation was in an Ubuntu WSL2 project (but I doubt that had anything to do with it)
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor