What is AMPDeviceDiscoveryAgent on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
AMPDeviceDiscoveryAgent is an Apple background agent that discovers iPhones, iPads and iPods attached to your Mac, so they can be shown and synced. It runs as your user, wakes when a device is connected, and is idle otherwise. It is part of macOS and safe.
AMPDeviceDiscoveryAgent at a glance
| AMPDeviceDiscoveryAgent | |
|---|---|
| Made by | Apple (part of macOS, AMPDevices framework) |
| Type | User agent |
| Location | /System/Library/PrivateFrameworks/AMPDevices.framework/Versions/A/Support/AMPDeviceDiscoveryAgent |
| Runs as | your user |
| Started by | launchd job com.apple.AMPDeviceDiscoveryAgent |
| Can you quit it? | Yes, but launchd starts it again, and connected devices may not appear in the Finder until it does. |
What is AMPDeviceDiscoveryAgent?
The man page describes AMPDeviceDiscoveryAgent as the per-user discovery service for iOS and iPod devices, with no configuration options. It is part of the AMPDevices private framework, which also contains a separate AMPDevicesAgent.
Device connections themselves go through usbmuxd; AMPDeviceDiscoveryAgent watches for devices appearing and tells the rest of the system about them.
Is AMPDeviceDiscoveryAgent safe?
Yes. It lives inside the AMPDevices framework in /System/Library on the read-only system volume and runs from an Apple launch agent.
Why does AMPDeviceDiscoveryAgent use so much CPU?
- Connecting an iPhone or iPad. Plugging in a device, or a device on Wi-Fi becoming available, makes it gather the device's details.
- A connection that keeps dropping. A faulty cable or port makes the device appear and disappear, and each appearance is processed again.
- Several devices. More connected or nearby devices mean more discovery work.
How much CPU is normal for AMPDeviceDiscoveryAgent?
Typical use is 0% CPU. A short burst when you connect a device is normal.
Sustained CPU use is not typical.
What can you do if AMPDeviceDiscoveryAgent is busy?
- Disconnect devices. Unplug iPhones and iPads you are not using and see whether it settles.
- Check the cable. If a device keeps reconnecting, try another cable or port.
- Quit it once. Select it in Activity Monitor and quit it. launchd starts it again when a device appears.
When should you worry about AMPDeviceDiscoveryAgent?
Constant CPU with no device connected is unusual; quit it once or restart. A copy outside the AMPDevices framework would not be Apple's.
How do you check AMPDeviceDiscoveryAgent in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type AMPDeviceDiscoveryAgent 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 AMPDeviceDiscoveryAgent process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'AMPDeviceDiscoveryAgent' | grep -v grep
How can Thrum help with AMPDeviceDiscoveryAgent?
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 AMPDeviceDiscoveryAgent 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 AMPDeviceDiscoveryAgent 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 AMPDeviceDiscoveryAgent
What does AMP stand for?
Apple does not document the name.
Can I remove it?
No. It is on the read-only system volume and is needed to detect connected devices.
Sources
- AMPDeviceDiscoveryAgent(8) man page: run man AMPDeviceDiscoveryAgent in Terminal