Thrum

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

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

ScreensharingAgent is the macOS process that works with screensharingd to give a remote computer access to your logged-in session when Screen Sharing or Remote Management is on. It uses CPU while someone is connected, because the session's screen has to be captured for the viewer. When nobody is connected it is normally not running.

ScreensharingAgent at a glance

ScreensharingAgent
Made byApple (part of macOS, Screen Sharing)
TypePer-user agent
Location/System/Library/CoreServices/RemoteManagement/ScreensharingAgent.bundle/Contents/MacOS/ScreensharingAgent
Runs asyour user
Started bylaunchd job com.apple.screensharing.agent
Can you quit it?Yes, but that interrupts a screen sharing session into your user session. It is started again for the next connection.

What is ScreensharingAgent?

Its man page says ScreensharingAgent communicates with screensharingd to provide access to a user session, and that Screen Sharing or Remote Management must be enabled to use it. screensharingd is the system daemon that accepts the network connection; ScreensharingAgent runs inside your login session, where it can see your windows and receive the viewer's mouse and keyboard.

launchd starts it through the com.apple.screensharing.agent job, which is limited to the normal desktop session and the login window, so a viewer can also see the login screen. The job is not set to run at load and waits for a notification from the screen sharing service.

Is ScreensharingAgent safe?

Yes, it is part of macOS, stored in /System/Library/CoreServices/RemoteManagement and signed by Apple as com.apple.screensharing.agent. It does nothing unless screen sharing is enabled and someone connects. If you see it running and did not expect a connection, check System Settings > General > Sharing.

Why does ScreensharingAgent use so much CPU and memory?

How much CPU is normal for ScreensharingAgent?

Without a connection, ScreensharingAgent should not be running. During a session, a moderate and changing CPU load is typical, higher when the screen changes a lot.

It should quit some time after the last viewer disconnects.

How do you stop ScreensharingAgent from using so much CPU?

  1. Disconnect the viewer. End the session from the screen sharing item in the menu bar, or close the window on the viewing computer.
  2. Reduce what changes on screen. Pause video playback and close animated content on the shared Mac during the session.
  3. Turn off Screen Sharing when you do not need it. Open System Settings > General > Sharing and turn off Screen Sharing. If Remote Management is on, it controls screen sharing too, so turn that off as well.
  4. Check the firewall state. The Sharing settings show Screen Sharing: Blocked by Firewall when the firewall stops incoming connections. If you want sharing off from the network, keep it off rather than relying on that state.

When should you worry about ScreensharingAgent?

Worry if ScreensharingAgent is busy when nobody should be connected. Turn Screen Sharing and Remote Management off and change the password of accounts allowed to connect.

A copy outside the RemoteManagement folder in /System/Library/CoreServices would not be Apple's.

How do you check ScreensharingAgent in Activity Monitor and Terminal?

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

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

How can Thrum help with ScreensharingAgent?

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

What is the difference between screensharingd and ScreensharingAgent?

screensharingd is the system daemon that accepts incoming screen sharing connections. ScreensharingAgent runs in your login session and gives that daemon access to your screen and input.

Why is ScreensharingAgent running when Screen Sharing is off?

Remote Management also uses it, and so can a management tool your organization installed. Check both settings in System Settings > General > Sharing.

Sources