Why is Cursor using so much CPU and memory on my Mac?
Last reviewed: 19 November 2026.
Cursor shares its editor design with VS Code (it imports VS Code settings and extensions and uses the same default shortcuts), so it runs extensions and language servers in helper processes that can use a lot of CPU and memory. Cursor's own troubleshooting says high usage typically stems from extensions or settings, and recommends testing with cursor --disable-extensions and adding large generated folders to .cursorignore. Commands that the Agent runs in the terminal, such as builds and test suites, also show up as separate processes.
What is using CPU when Cursor is busy?
- Extensions and language servers. Cursor installs extensions from the Open VSX registry. Each extension runs in the extension host, and language extensions start servers that index your project.
- Large generated folders. Build output such as
dist/,build/or.next/adds thousands of files for Cursor to track. - Agent commands. When the Agent runs terminal commands, the build tools, test runners and package managers it starts run as their own processes, for example node, python3 or git.
- Several windows. Each open project window adds its own renderer and extension processes.
How do you reduce Cursor's CPU and memory use?
- Test without extensions. Quit Cursor and run
cursor --disable-extensionsfrom Terminal. If usage drops, re-enable extensions one at a time to find the cause. - Remove extensions you do not need. Uninstall extensions for languages and tools you do not use in this project.
- Ignore generated folders. Create a
.cursorignorefile in the project root and list large generated folders such asdist/,build/and.next/. Cursor already respects.gitignoreand ignores.envfiles,.git/and lock files by default. - Check what the Agent started. In Activity Monitor, sort by % CPU and look for build, test or dev-server processes. A dev server or watcher started by an agent keeps running until it is stopped.
Does .cursorignore stop Cursor from reading a file?
It blocks the listed files from the Agent and from AI context. Cursor's documentation notes that terminal commands and MCP tools run outside its file access controls and may still be able to read ignored files. For performance, its main effect is that Cursor no longer pulls large generated files into context.
When should Cursor's resource use concern you?
A helper that stays at high CPU while you are not typing and no agent is running, or memory that keeps climbing with one small project open, is not typical. Restart Cursor first; if it returns, the extension test above usually finds the cause. Long-running processes left behind by agent sessions can be quit from Activity Monitor.
How can Thrum help with Cursor?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when Cursor is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click Cursor in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions
Can I run Cursor and VS Code at the same time?
Yes. Cursor's documentation says they run as separate applications and can be used on the same projects; each uses its own memory.
Does Cursor use VS Code Marketplace extensions?
Cursor uses the Open VSX extension registry. Many popular extensions are available, but not every VS Code extension is listed or works the same way.