What is KernelEventAgent on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1; it was running as root.
KernelEventAgent is the macOS program that shows user interface on behalf of the kernel: the warning that your disk is full and the dialog about a network file server that stopped responding. launchd starts it at boot and keeps it running, idle until one of those events happens. It is safe and should be left alone.
KernelEventAgent at a glance
| KernelEventAgent | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System daemon |
| Location | /usr/sbin/KernelEventAgent |
| Runs as | root |
| Started by | launchd job com.apple.KernelEventAgent |
| Can you quit it? | No. launchd keeps it running, and it is needed to warn you about a full disk or an unresponsive server. |
What is KernelEventAgent?
The kernel cannot draw dialogs itself. Its man page says KernelEventAgent is responsible for displaying disk full and unresponsive file server messages, and is meant to be started by the system without options. Its -t option sets how long it waits before warning again after you dismiss a notice about an unresponsive network mount.
launchd runs it as root through the com.apple.KernelEventAgent job with KeepAlive set, so it is always present in Activity Monitor's list of all processes.
Is KernelEventAgent safe?
Yes. It is an Apple-signed program in /usr/sbin on the read-only system volume. It only reacts to kernel events about disks and file servers.
Why does KernelEventAgent use so much CPU and memory?
- The startup disk is nearly full. When free space runs out, the kernel tells KernelEventAgent, which shows the warning. It may repeat while space stays low.
- A network share stopped responding. If a mounted file server goes away, for example after Wi-Fi drops, KernelEventAgent shows the dialog that lets you disconnect it.
- Always running. Because launchd keeps it alive, it holds a small amount of memory all the time.
How much CPU is normal for KernelEventAgent?
KernelEventAgent should sit at 0% CPU nearly all the time with a small memory footprint. It does work only when a disk or server event occurs.
Its CPU time grows very slowly over days of uptime.
What do you do about KernelEventAgent's warnings?
- Free up disk space. Open System Settings > General > Storage to see what uses space and remove what you do not need.
- Disconnect an unresponsive server. In the dialog about a server that is not responding, choose to disconnect it. Then reconnect from Finder when the network is back.
- Stop auto-mounting a server you no longer use. Remove server volumes from System Settings > General > Login Items & Extensions if they open at login and the server is gone.
When should you worry about KernelEventAgent?
KernelEventAgent itself using CPU continuously is not expected. The warnings it shows are the important part: a full startup disk can make apps fail and stop updates installing.
A copy outside /usr/sbin would not be Apple's.
How do you check KernelEventAgent in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type KernelEventAgent 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 KernelEventAgent process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'KernelEventAgent' | grep -v grep
How can Thrum help with KernelEventAgent?
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 KernelEventAgent 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 KernelEventAgent
Can I quit KernelEventAgent?
It is a root process that launchd keeps alive, so it starts again. There is no reason to quit it.
Why do I see a server not responding message?
A network share was mounted and the Mac lost contact with it. KernelEventAgent shows the message so you can disconnect it cleanly.
Sources
- KernelEventAgent(8) man page: run man KernelEventAgent in Terminal
- launchd job /System/Library/LaunchDaemons/com.apple.KernelEventAgent.plist on macOS 26.3.1