Cursor CLI burns > 100% CPU constantly

[Andy_Visser]

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

when the cursor CLI is sitting idle, it burn ~130%CPU on my M3 MBP.

Steps to Reproduce

Just bring up the CLI in a folder with a source project.

Expected Behavior

CPU usage is low-to-zero when not answering a question.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

$ cursor-cli --version
2025.11.06-8fe8a63

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the report. This is a known issue with cursor-agent version 2025.11.06-8fe8a63. The team is aware of it and is working on a fix.

[sam.saffron (Sam)]

note there are a ton of cross reports for this now:

Cursor agent consuming extremely high CPU

Additional info: [image] [image] This means that the GC is being triggered aggressively. See Link: https://meta.discourse.org/discourse-ai/ai-bot/shared-ai-conversations/q9-3kQLrzS4yDWDnfsKyqQ Particularly it could be issued by hand either by low memory notifications or if the bundled v8 in cursor agent exposes gc calls to js. Everything seems to be happening in MainThread fwiw (also, links are de-styled here, makes it very hard to tell if stuff is a link or not) FWIW this is Gemini 3s…

Runaway CPU in Cursor agent

Where does the bug appear (feature/product)? Cursor CLI Describe the Bug After running cursor CLI I notice CPU is high on my system (after exiting) There is a background node process eating up CPU Steps to Reproduce Run cursor-cli, perform some agent work, exit… high CPU is there Operating System Linux Current Cursor Version (Menu → About Cursor → Copy) ursor-agent --version 2025.09.12-4852336 Additional Information happy to try to get some extra debugging info. Does this stop you from u…

High CPU usage on Cursor CLI

Turns out this doesn’t work in MacOS. Try this instead: cd \~/.local/share/cursor-agent/versions/ mv {,bak.}2025.11.06-8fe8a63 ln -s 2025.10.28-0a91dc2 2025.11.06-8fe8a63 Before this I tried all sorts of shenanigans to prevent ~/.local/bin/cursor-agent from being overwritten: set uchg flag set ACL deny delete set ugo-w using chmod Turns out Apple doesn’t support any of these on APFS for symlinks.

---

This is not new to the current agent has been going on for months. GC is running non stop.

[user770]

This is by design