Thrum

What is CoreLocationAgent on my Mac?

Last reviewed: 19 November 2026. Path, launchd job, bundle and man page checked on macOS 26.3.1.

CoreLocationAgent is the macOS agent that shows location permission prompts, the dialogs that ask whether an app, daemon or widget may use your location. It is started by locationd and runs in your login session. It sits idle almost all the time.

CoreLocationAgent at a glance

CoreLocationAgent
Made byApple (part of macOS, Location Services)
TypePer-user agent (user interface)
Location/System/Library/CoreServices/CoreLocationAgent.app/Contents/MacOS/CoreLocationAgent
Runs asyour user
Started bylaunchd job com.apple.CoreLocationAgent
Bundle IDcom.apple.CoreLocationAgent
Can you quit it?Yes. locationd starts it again when it needs to show a location prompt.

What is CoreLocationAgent?

The CoreLocationAgent(8) man page says it manages the authorization prompts for apps, daemons and widgets that use location services, and that it is launched by locationd. locationd runs as a system account and cannot show windows in your session, so it hands the prompt to this agent.

It is an app bundle in /System/Library/CoreServices and runs as your user through the launchd agent com.apple.CoreLocationAgent. On the Mac checked here it was running at 0% CPU.

Is CoreLocationAgent safe?

Yes. It is part of macOS in /System/Library/CoreServices and is signed by Apple.

Why does CoreLocationAgent use so much CPU and memory?

How much CPU is normal for CoreLocationAgent?

Typical: 0% CPU, a small amount of memory, and running for most of the session.

Repeated prompts from the same app are a sign that the app keeps requesting location after you declined.

How do you stop repeated location prompts?

  1. Decide for the app once. Open System Settings > Privacy & Security > Location Services and set the app's switch on or off.
  2. Update the app. An app that keeps asking may have a bug that a newer version fixes.
  3. Check widgets. Widgets can request location too. Remove widgets you do not use, such as weather widgets for your current location.

When should you worry about CoreLocationAgent?

CoreLocationAgent is not a concern. A copy outside /System/Library/CoreServices would not be Apple's.

How do you check CoreLocationAgent in Activity Monitor and Terminal?

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

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

How can Thrum help with CoreLocationAgent?

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

Is CoreLocationAgent tracking my location?

No. It shows permission prompts. locationd determines the location, and only apps you allow receive it.

Why is it always running?

macOS keeps it available so a prompt can appear whenever an app asks. It uses almost no resources while waiting.

Sources