Guys we need a lite version of cursor.
I was not doing any updates and it kept showing me I am on my old version and I updated.
After updating everything is slow.
My computer is slow it has 16gb ram. I am broke I can’t buy something bigger than this now.
My client work is blocked. I am stuck at cursor hanging. I don’t have anything else running.
there is like 60-100 node process running. like why?
Take a look at the processor explorer. I also added a bunch of excluded files to the files.watcherExclude in vscode settings to try and minimize the background file watching process. But yea, Cursor can just eat a ton of resources on idle. VSCode is the same way, so may be just a VSCode issue.

Hey, let’s figure out what’s causing the slowdown. 60 to 100 Node processes is definitely not normal. Usually it’s one specific thing like extensions, MCP servers, language servers, or file watching over node_modules.
A few steps to find the culprit:
- Process Explorer:
Cmd+Shift+PorCtrl+Shift+Pthen run Developer: Open Process Explorer. Check which processes are using CPU or RAM, and pay extra attention to extensionHost and ptyHost. - Extension Monitor: Cursor Settings (not VS Code settings) > Application > Experimental > enable Extension Monitor, then
Cmd+Shift+PorCtrl+Shift+Pand run Developer: Open Extension Monitor. It’ll show which extension is using resources. - Quick test with no extensions: run
cursor --disable-extensionsfrom your terminal. If the lag is gone, it’s one of the extensions. - File watching: as MidnightOak mentioned, add heavy folders to files.watcherExclude in Settings, search for watcherExclude. Especially
**/node_modules/**,**/dist/**,**/.git/**. This can cut background load a lot.
If you share your Cursor version, OS, and what Process Explorer shows at the top, I can help more.
About a lite version, I’ve logged it as feedback. There isn’t a separate lightweight build right now, but the steps above usually reduce idle resource usage a lot.