What is nesessionmanager on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
nesessionmanager is the Apple daemon that starts and stops Network Extension sessions, such as VPN connections and content filters, and sets up the routes, DNS and policies each session needs. It runs while a VPN or filter is active and is busy mainly when sessions connect, disconnect or reconnect. It is part of macOS and safe.
nesessionmanager at a glance
| nesessionmanager | |
|---|---|
| Made by | Apple (part of macOS, Network Extension) |
| Type | System daemon |
| Location | /usr/libexec/nesessionmanager |
| Runs as | root |
| Started by | launchd job com.apple.nesessionmanager |
| Can you quit it? | Not usefully. Active VPN or filter sessions stop, and launchd starts it again when one is needed. |
What is nesessionmanager?
The man page says nesessionmanager is responsible for starting and stopping Network Extension sessions and for setting up and maintaining the network configuration and policy associated with them, naming VPN and content filter sessions.
It covers the built-in VPN types in System Settings as well as VPN apps. For an app-provided VPN, nesessionmanager decides when the session runs and applies its settings, while the app's own code runs in neagent or a system extension. Saved configurations come from nehelper.
Is nesessionmanager safe?
Yes. nesessionmanager lives in /usr/libexec on the read-only system volume and is started on demand by an Apple launch daemon.
Why does nesessionmanager use so much CPU?
- Connecting and disconnecting. Each connect or disconnect changes routes, DNS and policies, and configd recomputes the network state.
- On-demand and always-on VPNs. VPNs set to connect automatically for certain networks or domains make nesessionmanager evaluate rules whenever the network changes.
- Sleep, wake and network switches. Moving between Wi-Fi networks or waking from sleep makes sessions reconnect.
- Content filters. An active filter keeps a session running, so nesessionmanager stays loaded while it is on.
How much CPU is normal for nesessionmanager?
Typical use is 0% CPU with brief activity when a session connects or disconnects. It may not run at all on a Mac with no VPN or filter.
Repeated bursts every few seconds suggest a session that keeps failing and retrying.
How do you stop nesessionmanager from using so much CPU?
- Check which sessions exist. In System Settings, search for VPN and for Filters. Each listed configuration can start a session.
- Look for a reconnect loop. Run
scutil --nc listin Terminal to list VPN configurations and their status. A status that keeps changing points to a session that cannot stay connected. - Fix or remove the failing configuration. Update the VPN app, correct its server settings, or delete configurations you no longer use.
When should you worry about nesessionmanager?
Look closer if nesessionmanager is busy and you do not recognize any VPN or filter configuration. Remove configurations you did not add. A copy outside /usr/libexec would not be Apple's.
How do you check nesessionmanager in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type nesessionmanager in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every nesessionmanager process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'nesessionmanager' | grep -v grep
How can Thrum help with nesessionmanager?
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 nesessionmanager 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. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
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 nesessionmanager
Why is nesessionmanager running without a VPN?
Content filters and other Network Extension sessions also run through it, and some security or parental-control apps install one.
What is the difference between nesessionmanager and neagent?
nesessionmanager runs as root and manages sessions and network settings; neagent runs as your user and hosts the provider app's extension code.
Sources
- nesessionmanager(8) man page: run man nesessionmanager in Terminal
- scutil(8) man page: run man scutil in Terminal
- Apple Developer: Network Extension