What is CoreServicesUIAgent, and why is it using CPU?
Last reviewed: 19 November 2026. Path, account, launchd job, bundle ID and its dialog strings checked on macOS 26.3.1.
CoreServicesUIAgent is the macOS agent that shows CoreServices dialogs, including the "Verifying" progress window and the warnings when you open an app downloaded from the internet for the first time. It uses CPU while it verifies a newly downloaded app, which can take a while for large apps. It is safe, and it settles once verification finishes or you answer the dialog.
CoreServicesUIAgent at a glance
| CoreServicesUIAgent | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | Per-user agent (app bundle) |
| Location | /System/Library/CoreServices/CoreServicesUIAgent.app/Contents/MacOS/CoreServicesUIAgent |
| Runs as | your user |
| Started by | launchd job com.apple.coreservices.uiagent |
| Bundle ID | com.apple.coreservices.uiagent |
| Can you quit it? | Yes, but launchd starts it again the next time macOS needs to show one of its dialogs. |
What is CoreServicesUIAgent?
CoreServicesUIAgent is an app bundle in /System/Library/CoreServices that runs as your user from the com.apple.coreservices.uiagent launchd job. Its job provides two services, com.apple.coreservices.quarantine-resolver and com.apple.coreservices.code-evaluation.
Its own text resources show the dialogs it presents: the "Verifying …" progress window, "You are opening the application … for the first time. Are you sure you want to open this application?", "… is an app downloaded from the Internet" style warnings, the alert when an app contains malware, the prompt to install Rosetta to open an Intel app, the question when an app asks to become your default web browser, and the chooser for an app to open a file.
Is CoreServicesUIAgent safe?
Yes. It is part of macOS, signed by Apple, at /System/Library/CoreServices/CoreServicesUIAgent.app. The dialogs it shows are part of Gatekeeper, macOS's check of downloaded software, so read them before clicking Open.
Why does CoreServicesUIAgent use so much CPU and disk?
- Verifying a downloaded app. The first time you open an app downloaded from the internet, macOS checks it and shows a "Verifying" window. Large apps with many files take longer, and CPU and disk activity are high during the check.
- Reading the app being verified. Verification reads the files of the app, so a large app on a slow external drive keeps the dialog up longer.
- A dialog waiting for an answer. A first-open or warning dialog stays until you answer it. It may be hidden behind other windows while the app you tried to open appears not to start.
How much CPU is normal for CoreServicesUIAgent?
Typical: not running, or idle at 0% CPU. While a "Verifying" window is on screen, high CPU for seconds to a minute or two is normal for large apps.
If the "Verifying" window never finishes, or CoreServicesUIAgent is busy with no dialog visible, something is stuck.
What do you do when CoreServicesUIAgent is busy or stuck?
- Wait for verification. Let the "Verifying" window finish. Copy large apps to the Applications folder on the internal disk first; verifying from a disk image or slow drive takes longer.
- Look for a hidden dialog. Press Command-Tab or use Mission Control to find a CoreServicesUIAgent dialog behind other windows, and answer it.
- Quit it if verification hangs. If the window stays for many minutes, quit CoreServicesUIAgent in Activity Monitor and open the app again. launchd starts a fresh copy.
- Check the Privacy & Security settings. If an app is blocked, System Settings > Privacy & Security shows a message about it with an Open Anyway button. Use it only for software from a source you trust.
When should you worry about CoreServicesUIAgent?
Take its warnings seriously: a dialog saying an app contains malware, or cannot be checked for malware, means macOS found a reason not to trust it. Move the app to the Trash unless you know where it came from.
A process with this name outside /System/Library/CoreServices would not be Apple's.
How do you check CoreServicesUIAgent in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type CoreServicesUIAgent in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every CoreServicesUIAgent process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'CoreServicesUIAgent' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
How can Thrum help with CoreServicesUIAgent?
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 CoreServicesUIAgent 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 CoreServicesUIAgent 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 CoreServicesUIAgent
Why does my Mac say "Verifying" when I open an app?
The app was downloaded, and macOS checks it the first time it opens. CoreServicesUIAgent shows the progress of that check.
Is it safe to quit CoreServicesUIAgent?
Yes, if a dialog is stuck. Any open dialog closes without an answer, and the agent starts again when needed.
Sources
- CoreServicesUIAgent.app resources (FirstLaunch, GatekeeperProgressStrings, Quarantine, OAH, ChangeDefaultHandler .loctable files), read on macOS 26.3.1
- launchd job com.apple.coreservices.uiagent: run launchctl print gui/$(id -u)/com.apple.coreservices.uiagent