Hi, thanks for reporting! We have an open bug ticket for this issue on Windows (I know you’re on Mac). Would you mind sharing the cursor version info ? You can grab it by going to Cursor → About Cursor and copying the version information you see there. This will help us clarify the impacted versions.
Version: 3.3.8
VSCode Version: 1.105.1
Commit: d1553adb2e976c19f71d5530c5a9d9b25ccf4e70
Date: 2026-05-05T04:55:15.349Z (1 day ago)
Layout: editor
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin x64 24.6.0
Ok cool, thank you.
We shipped out an update for this ticket that should alleviate the issue on Windows. Are you still seeing the same behavior currently?
I am on macOS, latest version issue still exists.
Version: 3.3.17
VSCode Version: 1.105.1
Commit: 7802cd697cf92bf53d0b4aa590925c696eb51720
Date: 2026-05-06T21:33:12.996Z (13 hrs ago)
Layout: editor
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin x64 24.6.0
still exists
Version: 3.5.3
VSCode Version: 1.105.1
Commit: cc934b516e20cc58a8eabb10d300918fc02b3a20
Date: 2026-05-16T22:03:17.373Z (1 day ago)
Layout: editor
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin x64 24.6.0
hey @gengjiawen just to confirm, on what version of cursor are you now? some major and non major update have come up since (tho idk if the bug where indeed fixed or not)
Version: 3.7.19
VS Code Extension API: 1.105.1
Commit: 80c653c2c3528e65016a0d304b54486084b470b0
Date: 2026-06-07T01:42:56.126Z (2 days ago)
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0
This takes too long to fix 
:(( will ping the team about it
Thanks for keeping the version info coming, @gengjiawen and sorry this has dragged on for so long.
To clear up where things stand: the fix that shipped earlier was for a Windows-specific version of this problem. The macOS idle polling you’re capturing - the repeated GetTeams / full_stripe_profile / metrics calls firing every second or two while the app just sits idle - is a separate issue on our side, and your latest capture on 3.7.19 (plus @bbur’s) confirms it’s still happening. This isn’t anything on your end.
I’ve raised this with our team to track separately from the Windows fix. No ETA to share yet, but the Process Explorer captures you’ve both posted are exactly what’s needed to chase it down.
One thing that would help narrow it: when you grab these captures, do you have multiple Cursor windows open, or are you connected to any Remote (SSH / WSL / Dev Container)? Multiple windows or a remote connection each add their own background syncing, so knowing your setup helps us tell whether it’s one loop misbehaving or several stacking up.
I opened multiple window with ssh dev enviroment.
Issue still exists on:
Version: 3.8.11
VS Code Extension API: 1.105.1
Commit: e56ad3440df06d22ca7501e65fd518e905486ef0
Date: 2026-06-18T01:40:18.333Z (4 days ago)
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0
Following up — still seeing this on a much later version than originally reported here.
Version: 3.9.8 (Commit 4aa8ff1b7877ed7bd01bcba308698f71a6735380, Electron 40.10.3, Darwin arm64 25.5.0)
Battery dropped 100%→37% in 2.5 hours. Activity Monitor Energy tab (12hr Power) showed Cursor at 7,782 while every other app was in the double/triple digits. Did a full update + restart expecting it to resolve — instead it got worse on the next session: 9,202 (12hr Power), still far above everything else running.
@kevinn — given this thread says the issue was “addressed” back in May (v3.3.8) but I’m still hitting it hard on 3.9.8 in June, is this a regression, or a separate issue that looks the same from Activity Monitor’s perspective? Happy to provide a Sample Process capture if useful.
Hi @Moody Thanks for following up, and sorry this is still affecting you.
A Sample Process capture would be useful. Feel free to capture the Cursor Helper (Renderer) process showing the highest Energy Impact while Cursor is idle and attach the output. Could you also confirm:
Thank you!
