What is Code Helper (Plugin), and why is it using so much CPU?
Last reviewed: 19 November 2026. Helper bundles, bundle IDs and the extension host launch options checked in Visual Studio Code 1.138 on macOS 26.3.1.
Code Helper (Plugin) is the Visual Studio Code process that runs the extension host, the process where your extensions run. When it uses a lot of CPU or memory, an extension is almost always the cause: a language server starting, a linter scanning the workspace, or an extension stuck in a loop. VS Code's Running Extensions view and Extension Bisect find which one.
Code Helper (Plugin) at a glance
| Code Helper (Plugin) | |
|---|---|
| Made by | Microsoft (part of Visual Studio Code) |
| Type | Helper process (VS Code extension host) |
| Location | /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) |
| Runs as | your user |
| Bundle ID | com.microsoft.VSCode.helper |
| Can you quit it? | Yes. Extensions stop working in that window until you run Developer: Restart Extension Host or reload the window. |
What is Code Helper (Plugin)?
VS Code's documentation says the extension host is responsible for running extensions and keeps misbehaving extensions from slowing down the interface. VS Code starts the local extension host as an Electron utility process with the option to load unsigned libraries, and Electron's documentation says that option launches the process through the Helper (Plugin).app helper on macOS, which can be signed with the entitlements needed for that. That is why the extension host appears as Code Helper (Plugin).
Each VS Code window has its own extension host. Extensions often start further processes of their own, such as language servers, which appear as separate processes with the extension host as their parent.
Is Code Helper (Plugin) safe?
Yes, when it runs from inside Visual Studio Code.app. What it runs is the extensions you installed, so a busy extension host is a question of which extension, not of VS Code itself.
Why does Code Helper (Plugin) use so much CPU and memory?
- Language extensions indexing. Language support for TypeScript, Python, Swift and others analyzes the workspace when you open it, often through a language server started by the extension.
- Linters, formatters and test runners. Extensions that lint on every change, discover tests or scan the whole workspace use CPU in proportion to the size of the project.
- Many installed extensions. Every activated extension loads its code into the extension host. VS Code activates extensions lazily, but a large set still adds memory.
- A misbehaving extension. VS Code's performance guide says that if the extension host is using a lot of CPU, this is likely caused by an extension.
How much CPU is normal for Code Helper (Plugin)?
High CPU for a while after opening a workspace, then low CPU while you edit, is the usual pattern.
One extension host per window, plus any language servers started by extensions.
How do you find the VS Code extension that is using CPU?
- Show running extensions. Open the Command Palette and run Developer: Show Running Extensions. It lists active extensions and lets you record a CPU profile of the extension host.
- Bisect extensions. Run Help: Start Extension Bisect and answer Good now or This is bad after each round until VS Code names the extension responsible.
- Start without extensions. Run
code --disable-extensionsin Terminal. If CPU stays low, the cause is an extension. - Disable or replace the extension. Disable the extension for this workspace, or report the problem on its Marketplace page with the profile you recorded.
When should you worry about Code Helper (Plugin)?
A Code Helper (Plugin) that stays near 100% CPU with the workspace idle points to an extension in a loop. Restarting the extension host clears it for the moment; bisecting finds the cause.
Extensions run with your user's permissions. Remove extensions you do not recognize or no longer use.
How do you check Code Helper (Plugin) in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type Code Helper (Plugin) in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every Code Helper (Plugin) process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'Code Helper (Plugin)' | grep -v grep
How can Thrum help with Code Helper (Plugin)?
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 Code Helper (Plugin) 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 Code Helper (Plugin) 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 about Code Helper (Plugin)
Why is it called Plugin?
The name comes from Electron's Helper (Plugin) app, which Electron uses for utility processes allowed to load unsigned libraries. VS Code starts its extension host with that option.
Can I restart the extension host without restarting VS Code?
Yes. Run Developer: Restart Extension Host from the Command Palette, or Developer: Reload Window to reload the whole window.