Where does the bug appear (feature/product)? Cursor CLI Describe the Bug Once I updated to the november usage, just starting the cursor cli takes 100% of a single core which starts the laptop fan running. I’m surprised nobody here complains. Steps to Reproduce Just start the CLI in WSL (Ubuntu 22.…

It’s all pretty clean. I use fish shell, maybe that’s important. I’ve tried running it in Bash now, same results. I tried what you suggested as well, too, mv .bashrc .bashrc.bak. I’ve lost all the color in my console as a result but the CPU usage is still the same. Maybe there’s a way to get the cal…

I got the same issue here. My cli version is 2025.11.06-8fe8a63

I have the same issue with cursor-agent version 2025.11.06-8fe8a63 also on fish shell. I let my AI diagnose the Issue and it came up with this: Summary cursor-agent (build 2025.11.06-8fe8a63) pegs a CPU core on Linux even while idle. Strace shows the main thread stuck in a zero-timeout epoll…

this app is turning into slopware more and more with every passing day

UPD: here’s the workaround (downgrade to previous version without the bug): ln -sf ~/.local/share/cursor-agent/versions/2025.10.28-0a91dc2/cursor-agent ~/.local/bin/cursor-agent This bug is not fixed for more than 2 weeks… Awful. They know they are invincible and people will continue using their p…

Same on macOS with the latest and previous cursor-agent versions. 100% CPU in idle state. And if I forget to /exit and keep it running for few hours it sometimes hit 150% CPU. Apple M1 Max, macOS 15.6.1 (24G90), cursor-agent 2025.11.06-8fe8a63

Thanks man! you are a life saver.

Cursor is an expensive product, that too with a subscription model. It’s been 13 days since the broken 11-06 update was rolled out and yet no fix in sight. This is unacceptable.

UPD 2: after a while it forcibly overwrites this symlink back to the buggy newest version :man_facepalming: To prevent this, make sure the symlink is owned by root, so that this expensive piece of software will have no permission to overwrite it. sudo chown root:root ~/.local/bin/cursor-agent

I just run it like this: ~/.local/share/cursor-agent/versions/2025.10.28-0a91dc2/cursor-agent There’s no need for symlink.

High CPU usage on Cursor CLI

Support Bug Reports

sam.saffron (Sam) November 19, 2025, 8:52pm 16

also reported and acknowledged here:

Topic		Replies	Views
Cursor CLI burns > 100% CPU constantly Bug Reports cli	4	252	December 14, 2025
Cursor stuck in "Generating..." + high CPU usage Bug Reports cli	3	169	December 11, 2025
Cursor agent consuming extremely high CPU Bug Reports cli	3	135	December 12, 2025
Cursor CLI (cursor-agent) slow and using 100% of a single cpu Bug Reports cli	2	319	November 16, 2025
Runaway CPU in Cursor agent Bug Reports cli	3	77	October 13, 2025

High CPU usage on Cursor CLI

Related topics