← Mac guides

How to quit Cursor and Windsurf helpers cleanly on Mac

Closing every window in Cursor or Windsurf leaves macOS apps—and their Electron, language-server, and MCP helper processes—running in memory. Here is how to verify a clean exit.

Updated 2026-11-19 · Applies to Cursor, Windsurf, Kiro, Trae, and Void on macOS

Why closing windows leaves helpers alive on macOS

Unlike Windows, closing the last window of a macOS Electron IDE keeps the parent app alive in the Dock. Its extension host, GPU helper, and local MCP server children can continue consuming gigabytes of unified RAM and keeping connections open.

Step-by-step clean quit & verification

  1. Save open buffers and stop any running agent turns or Cascade tasks.
  2. Focus each IDE and press Command + Q (verify the Dock indicator dot disappears).
  3. Run a read-only check in Terminal for any remaining bundle helpers:
ps -eo pid,ppid,rss,comm,args | grep -Ei "Cursor[.]app|Windsurf[.]app|Kiro[.]app|Trae[.]app|Void[.]app" | grep -v grep

If an orphaned helper remains after the main app exited, quit it by PID in Activity Monitor or Terminal (kill PID).

Check global MCP configs before switching projects

Even after a clean quit, reopening Cursor or Windsurf immediately reloads global MCP configs from ~/.cursor/mcp.json or ~/.codeium/windsurf/mcp_config.json. See our complete Mac MCP config path table.

Pause Cursor, Windsurf, and their MCP configs together

AI Stopper matches executables inside Cursor.app, Windsurf.app, Kiro.app, Trae.app, and Void.app along with every descendant helper process, snapshots supported MCP configs locally, and prevents accidental restarts via Restart Guard.