What is Code Helper (Renderer) on Mac?

What it is

Visual Studio Code is built on Electron (Chromium plus Node.js). Its processes, inside /Applications/Visual Studio Code.app/Contents/Frameworks/, are:

Process	Job
Code Helper (Renderer)	One per window. The workbench UI: editor, file tree, terminal panel rendering, webviews.
Code Helper (Plugin)	The extension host, one per window. Runs extensions.
Code Helper (GPU)	Compositing and drawing.
Code Helper	Utility work: file watcher, shared processes, integrated terminal’s pty host.

Language servers (the TypeScript server, Pylance, rust-analyzer, gopls) appear as child processes, sometimes as Code Helper (Plugin) and sometimes under their own names like node.

Why it uses CPU and memory

• An extension: linters on every keystroke, Git extensions on huge repos, AI completion extensions, theme or icon extensions doing too much.
• Language servers on big projects: TypeScript in a monorepo, or Python analysis over a large virtualenv.
• File watching: node_modules, dist and .git across a large workspace mean lots of FSEvents (fseventsd).
• Search indexing across large folders.
• The renderer itself: huge files open, minimap on a 100k-line file, a webview (Markdown preview, notebook) with heavy content, or a terminal printing nonstop.

How to find the culprit

1. Help › Open Process Explorer shows every VS Code process with CPU and memory, labeled (window, extension host, each language server). Same as code --status in Terminal.
2. Run Help: Start Extension Bisect from the Command Palette. It disables half your extensions at a time until it finds the one causing the problem.
3. Developer: Show Running Extensions lists activation times and flags extensions that are profiling as slow.

How to make VS Code calm down

1. Exclude heavy folders from watching and search in settings.json:

{
  "files.watcherExclude": {
    "**/node_modules/**": true,
    "**/dist/**": true,
    "**/.git/objects/**": true
  },
  "search.exclude": { "**/node_modules": true, "**/dist": true }
}

2. Disable extensions per workspace instead of globally, so a Python project doesn’t load your Go tooling.
3. Restart the language server: TypeScript: Restart TS Server or the equivalent for your language.
4. Close windows you aren’t using: each one has its own renderer and extension host.
5. Update VS Code. Performance fixes land monthly.

When to worry

Confirm the helpers belong to Microsoft’s build:

codesign -dv --verbose=2 "/Applications/Visual Studio Code.app" 2>&1 | grep -E 'Authority=Developer|TeamIdentifier'

Expect Developer ID Application: Microsoft Corporation (UBF8T346G9). More relevant than the binary: extensions run with your full user permissions. Install them from publishers you trust, and remove ones you don’t recognize.

Seeing it in Stat Space

Stat Space groups all the Code Helper processes under Visual Studio Code (or Cursor) in the Apps tab, labels each helper by its Electron role (renderer, GPU, utility), and shows a combined total. Dev servers and agents started from VS Code’s terminal show VS Code as their launcher in the Ports and Agents tabs, so you can tell what’s really the editor and what’s your code running inside it.