What is appleeventsd, and why is it using CPU?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
appleeventsd is the system-wide macOS daemon that coordinates most Apple events between applications, the messages AppleScript, Shortcuts and automation tools use to control other apps. It gets busy when scripts or apps send many such events, for example an automation tool polling another app. Find and slow down the script or app, and appleeventsd goes back to idle.
appleeventsd at a glance
| appleeventsd | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System daemon |
| Location | /System/Library/CoreServices/appleeventsd |
| Runs as | _appleevents (a system account) |
| Started by | launchd job com.apple.coreservices.appleevents |
| Can you quit it? | Not usefully. launchd starts it again, and scripts and apps that talk to each other need it. |
What is appleeventsd?
The appleeventsd(8) man page describes it as a system-wide daemon which coordinates AppleEvents activity on the system and acts as the daemon for most Apple events between applications. Apple events are how one app asks another to do something: AppleScript's tell application, many automation utilities and some app integrations use them.
It runs as its own system account, _appleevents, from the com.apple.coreservices.appleevents launchd job. When an app first tries to control another app, macOS asks for your permission; those choices are listed in System Settings > Privacy & Security > Automation.
Is appleeventsd safe?
Yes. appleeventsd is part of macOS at /System/Library/CoreServices/appleeventsd on the read-only system volume and runs as a restricted system account.
Why does appleeventsd use so much CPU?
- A script or tool sending events in a loop. An AppleScript, Shortcuts automation or menu bar utility that asks another app for information every second sends a stream of Apple events.
- Apps integrating with each other. Apps that read data from Music, Mail, Finder or a browser through scripting, such as now-playing or window-management utilities, generate events continuously.
- A target app that is not responding. If the app receiving events is hung, the sender may retry, and the events pile up.
How much CPU is normal for appleeventsd?
Typical: near 0% CPU, with brief activity when a script runs.
Steady CPU use means some process sends Apple events continuously.
How do you find what is sending Apple events?
- Review Automation permissions. Open System Settings > Privacy & Security > Automation. Each app listed there has asked to control other apps; the list narrows down the senders.
- Quit automation tools one at a time. Quit menu bar utilities, script runners and apps that integrate with other apps, one at a time, and watch appleeventsd's CPU.
- Stop running scripts. Check Script Editor, Shortcuts and any scheduled scripts for one that loops. Add a delay between repeated requests or stop it.
- Check whether the target app is hung. If an app shows as Not Responding in Activity Monitor, quit it; events sent to it stop.
When should you worry about appleeventsd?
Worry if appleeventsd stays busy after you quit every automation tool, or if you see an unfamiliar app in the Automation list. Remove permission for apps you do not recognize.
An appleeventsd outside /System/Library/CoreServices would not be Apple's.
How do you check appleeventsd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type appleeventsd 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 appleeventsd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'appleeventsd' | grep -v grep
How can Thrum help with appleeventsd?
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 appleeventsd 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 appleeventsd
Why does my Mac ask if an app may control another app?
Apple events let one app automate another, so macOS asks first. Apple's guide says you can review and change these choices in Privacy & Security > Automation.
Does appleeventsd run my scripts?
No. It coordinates the events scripts send. The script runs in the app that executes it, such as Script Editor or Shortcuts.
Sources
- appleeventsd(8) man page: run man appleeventsd in Terminal
- Apple Support: Allow apps to control your Mac (Automation)