Thrum

What is UserEventAgent, and why is it using CPU on my Mac?

Last reviewed: 19 November 2026. Path, accounts, launchd jobs, plugin folder and man page checked on macOS 26.3.1.

UserEventAgent is a macOS daemon that loads system plugins to handle high-level events that launchd cannot watch directly, such as device, network and power changes. It is normally quiet, and CPU use follows bursts of such events, for example connecting devices, changing networks or waking from sleep. Ongoing high CPU usually means one event source keeps firing.

UserEventAgent at a glance

UserEventAgent
Made byApple (part of macOS)
TypeSystem daemon and per-user agent
Location/usr/libexec/UserEventAgent
Runs asroot, plus copies as your user
Started bylaunchd job com.apple.UserEventAgent-System (root) and com.apple.UserEventAgent-Aqua, -LoginWindow and -CryptexContainer (per user)
Can you quit it?Not usefully. launchd keeps it alive and restarts it.

What is UserEventAgent?

The UserEventAgent(8) man page describes it as a high-level system event handler: a daemon that loads system-provided plugins to handle events that cannot be monitored directly by launchd. Its plugins live in /System/Library/UserEventPlugins; on this Mac they include plugins for Bluetooth, Bonjour, disk arbitration, IOKit device matching, file-system events, network reachability, system configuration, time, printers, memory and Time Machine.

The plugins turn those events into launch triggers, so that a launchd job can say "start me when this device appears" or "start me when the network changes". One copy runs as root for the system (com.apple.UserEventAgent-System) and others run in your login session (com.apple.UserEventAgent-Aqua and related jobs).

Is UserEventAgent safe?

Yes. UserEventAgent is part of macOS at /usr/libexec/UserEventAgent, and its plugins are in the read-only /System/Library/UserEventPlugins folder. The man page says it should not be invoked directly.

Why does UserEventAgent use so much CPU?

How much CPU is normal for UserEventAgent?

Typical: near 0% CPU, with brief spikes when devices connect, the network changes or the Mac wakes.

Continuous CPU use while nothing is being plugged in or changing is not normal.

How do you narrow down what keeps UserEventAgent busy?

  1. Check which copy is busy. In Activity Monitor, choose View > All Processes and add the User column. The root copy handles system events; a copy running as you handles events for your session.
  2. Disconnect devices one at a time. Unplug docks, hubs, USB devices and drives one at a time and turn off Bluetooth accessories you are not using. A faulty cable or device that keeps reconnecting is a common source of repeated device events.
  3. Check the network. If Wi-Fi keeps dropping and reconnecting, or a VPN keeps reconnecting, each change fires events. Fix the connection or quit the VPN app and watch CPU.
  4. Sample it. In Activity Monitor, select UserEventAgent and choose View > Sample Process. Plugin names such as com.apple.iokit.matching or SCMonitor in the sample show which plugin is doing the work.

When should you worry about UserEventAgent?

Worry if UserEventAgent stays busy for long periods with nothing changing, especially together with log messages about a device attaching and detaching repeatedly. That is usually hardware or a cable.

Files named UserEventAgent outside /usr/libexec, or extra plugins outside /System/Library/UserEventPlugins, would not be Apple's.

How do you check UserEventAgent in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type UserEventAgent 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 UserEventAgent process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'UserEventAgent' | grep -v grep

How can Thrum help with UserEventAgent?

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 UserEventAgent 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 UserEventAgent

Why are there several UserEventAgent processes?

One runs as root for system-wide events and others run in your login session, each started by its own launchd job.

Can I remove UserEventAgent plugins?

No. They are on the read-only system volume and macOS needs them to start services when events happen.

Sources