# How much RAM is Cursor using on my Mac?

> Cursor splits into dozens of helper processes, so Activity Monitor hides the total. Here's how to see how much memory Cursor is really using on a Mac.

**Quick answer:** Add up every Cursor process, not the biggest row. Cursor splits into helpers the same way VS Code does. In one real reading, Cursor was 35 processes using 2.64 GB. Bondi's Stack tab shows that total, and lists Claude Code and Codex beside it.

By Noaman Khalil, maker of Bondi. Published November 9, 2026.
Web page: https://trybondi.app/blog/cursor-memory-mac/

Cursor, like VS Code, splits itself into dozens of helper processes. Activity Monitor's Memory tab then shows a pile of "Cursor Helper" rows, none of them huge, and the real total is easy to miss. To see how much RAM Cursor is using on a Mac, add every one of those processes up.

## Key points

- Cursor's memory is the sum of the app plus every Cursor Helper, renderer, plugin and node process.
- In one real reading, Cursor was **35 processes using 2.64 GB**. The biggest single row was 548.4 MB.
- Bondi's Stack tab lists Cursor under **AI Agents**, and VS Code and Xcode under editors, each as one row.

## One reading, with Cursor open

This is the Mac I measure on: a 14-inch MacBook Pro (M1 Max, 64 GB), 16 October 2026, memory pressure Normal. Cursor was in use, Visual Studio Code had folders open, and Xcode was sitting idle.

| App | Processes | Memory |
| --- | --- | --- |
| Google Chrome | 71 | 6.79 GB |
| Visual Studio Code | 36 | 4.37 GB |
| Cursor | 35 | 2.64 GB |
| Xcode | 3 | 118.3 MB |

*Grouped by Bondi. Chrome is here to show the scale: the IDEs were not the heaviest thing running.*

The biggest Cursor row in that reading was **Cursor Helper at 548.4 MB**. Next was a renderer at 498.6 MB, then plugin helpers around 200 MB. None of those rows is the answer. Together they were **2.64 GB**, and Cursor was using **62.7% of one CPU core** at that moment.

That is one Mac, in the middle of work. A quiet window uses less; a long agent session with several workspaces open uses more. The number to watch is still [memory pressure](https://trybondi.app/blog/memory-pressure-explained/): green means the Mac is comfortable, even if Cursor looks large.

## How to add it up in Activity Monitor

1. Open **Activity Monitor** and choose the **Memory** tab.
2. Type **Cursor** in the search field. You should see Cursor, Cursor Helper, Cursor Helper (Renderer), Cursor Helper (Plugin) and often a few `node` processes.
3. Choose **View → All Processes, Hierarchically**. Helpers sit under the app that started them.
4. Expand Cursor and add the rows. Activity Monitor doesn't give you a total.

The same trick works for **Visual Studio Code** (look for Code Helper) and **Xcode**. Typing the name filters the list; it doesn't add the numbers.

## IDEs and AI agents are not the same list

On this Mac, Bondi's Stack tab splits them:

**Editors** are the apps you type in: Visual Studio Code, Xcode, Windsurf, Zed, Sublime Text, JetBrains IDEs. Cursor is left off that list on purpose, so it isn't counted twice.

**AI Agents** are Cursor, Claude Code and Codex, in that order. Cursor is the whole app, helpers included. Claude Code and Codex are the sessions running in a folder.

In the same reading:

| Agent | What it was | Memory |
| --- | --- | --- |
| Cursor | The app, 35 processes | 2.64 GB |
| Claude Code | Three sessions | 260.9 MB, 209.7 MB, 206.5 MB |
| Codex | Two sessions | 26.0 MB, 24.6 MB |
| All of them | | **3.35 GB** |

Claude Code's processes also sit under Visual Studio Code in the app list, because that is where those sessions were started. Bondi still shows them on the Agents card.

No local model was running. When one is, Stack lists it with the memory it holds. The [LLM RAM calculator](https://trybondi.app/can-my-mac-run-it/) works out what fits before you download.

## Does it matter?

Only if memory pressure is yellow or red. With green pressure, Cursor is using memory macOS has spare. If pressure climbs, the grouped total tells you whether Cursor, VS Code, Chrome or a local model is the lever: close a workspace, quit the agent, or restart the app after a long session.

## Questions

### How much RAM does Cursor use on a Mac?

It depends what you have open. In one reading on an M1 Max, Cursor was 2.64 GB across 35 processes, with VS Code at 4.37 GB on the same Mac. Add every Cursor Helper row; the biggest one is not the total.

### Why does Cursor have so many processes on a Mac?

Cursor is built like VS Code. Each window, extension and some AI work runs in its own process, so one misbehaving piece can't take the rest down. Activity Monitor then shows many Cursor Helper rows instead of one total.

### How do I see Cursor's total memory in Activity Monitor?

Memory tab, search for Cursor, then View → All Processes, Hierarchically, and add the rows under Cursor. Bondi groups them into one row on Stack, under AI Agents.

### Is Cursor an IDE or an AI agent?

Both. It is an IDE (a VS Code-style editor), and the agent is why people use it. Bondi lists it under AI Agents so the whole app is one total, and so it isn't counted again next to VS Code.

---
Bondi is a native macOS system monitor with on-device AI. It tells you why your Mac is slow, in one plain sentence. https://trybondi.app/