Background agent keeps turning on itself

Describe the Bug

The ‘Running agent in clouds’ option really slows down Cursor UI
I try to switch it off in the settings but in some time it’s again on
How to disable it?

Steps to Reproduce

Switch it off
In some time it will be on again

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.0.0 (user setup)
VSCode Version: 1.96.2
Commit: 53b99ce608cba35127ae3a050c1738a959750860
Date: 2025-06-04T19:44:25.253Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 Likes

also it takes over ctrl+e which I used for finding files. annoying :grin: :grin: :grin:

Hey both, appreciate the feedback!
I’ve flagged both of these to the team to look into.

@altrusl I don’t believe the Background Agent should cause the editor to slow down, especially if you are not using it! Would you say you use Cursor on a slower than ideal network / machine? The Background Agent may do some stuff in the background to check whats going on, but shouldn’t have much of an impact as far as I know.

@cocode Good shout, sorry for stealing your keybind! You should be able to manually change the shortcut in the usual VSCode-style way, but I get that is a bit annoying to have to do - will talk to the team

Hello @danperks

Same network, same machine, same projects - only the cursor version has changed.

I’m more than sure it’s Background Agent, because I turned it off, it got much better, then it started lagging again, CTRL + TAB takes 3-4 seconds, I go to Settings, and the switch is back on. I’ve checked this dozens of times.

According to Windows Task Manager there are no problems with memory or CPU utilization. So it’s probably the network. I kind of noticed when working over a mobile network - when it’s busy enough (in the evening), Cursor lags much more than when it’s not (early in the morning)

Also running 2-3 simultaneous Cursor instances at the same time makes it seem to make things worse.

Maybe you’ve started some new servers that my network might be having problems with?

But in any case, the network connections must not interfere with the UI thread. I feel like I got into Android Studio 10 years ago on a slow computer

Please release a patch with a fix for that switch. And then it will be possible to say more definite about the problem. In any case it shouldn’t be like this.

Hey, so I believe this may be linked to this ongoing thread, so I’d keep track of that for now and let me know if your issues are or are not solved once that thread is resolved soon!