Hey there!
What you’re describing isn’t intended behavior, and it’s not something in your setup. We’ve let the team know and this is an issue we’re tracking.
While that’s being looked at, a couple of settings should tame the CPU right away.
1. Cap ripgrep’s threads. In your settings.json:
"search.ripgrep.maxThreads": 1
By default each search process uses every core, so a few of them running at once peg the CPU. This is the single biggest lever (you can bump it to 2 if search feels slow).
2. Keep heavy folders out of search and indexing. Also in settings.json:
"search.followSymlinks": false,
"search.exclude": {
"**/node_modules": true,
"**/.next": true,
"**/dist": true
}
Then add the same folders to a .cursorignore at your project root so agent and indexing skip them too: Ignore Files.
After changing these, run Command Palette → Reload Window so the search processes restart clean.
Give that a try and let me know if the CPU settles. Happy to dig in further if it doesn’t.