Cursor helper keeps opening git and using 90%+ of CPU

[Dima_Shkabura]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Whenever I use the agent, it keeps on opening up Git, and I’m not sure exactly when this happens. But at some point, when I open up my Task Manager, there are 5-7 Gits just open, each one of them using 80-90% of my CPU and if I don’t close them in time and forget to do it, my computer loses charge really quickly and becomes slow. At which point I do notice it and realize that I’ve just used up like 50% to 60% of my battery in less than an hour.

Steps to Reproduce

For me, it just happens when I use the agent.

Expected Behavior

I would like Cursor to either use Git in an efficient way or to not use it at all.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.38
VSCode Version: 1.99.3
Commit: 3fa438a81d579067162dd8767025b788454e6f90
Date: 2025-10-29T20:45:40.883Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Composer
Claude

Happens with all models

Additional Information

This is super annoying because it:

1. Really slows down Cursor if I don’t notice it
2. Destroys my battery and my CPU
3. Forces me to have my Activity Monitor open all the time to monitor this.

This was also happening for a really long time. Like I’ve created this account, but it’s been happening for 3-4 months already. I’m at this point just got so annoyed that I really want this to be fixed.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[sanjeed5 (Sanjeed)]

Thanks for the screenshot @Dima_Shkabura! The git processes are being spawned by the extension-host, which probably points to an extension issue. This is very similar to this bug where hundreds of rg processes were spawned - users traced it to specific extensions.

To identify the culprit:

1. Enable Extension Monitor:

• Go to Settings > Application > Experimental
• Toggle “Extension Monitor: Enabled” and restart Cursor
• Open it: Cmd + Shift + P → “Developer: Open Extension Monitor”
• This will show which extension is launching those git processes

2. Or use Extension Bisect (faster):

• Cmd + Shift + P → “Extension Bisect”
• Follow the prompts to identify the problematic extension

3. Quick test: Run cursor --disable-extensions from terminal - if the issue goes away, it’s definitely an extension

Once you identify it, please share:

• Which extension is causing it
• Request ID: Getting a Request ID | Cursor Docs (reproduce first, then grab ID)

Please let us know if it’s not due to any of the extensions, thank you!