HeartbeatHocusFocusFilesMacHyperTile
Guide

remoted, the daemon that finds devices for other daemons

remoted discovers remote devices and services for macOS, from Xcode's device tools to the firewall allow list. Measured on a real Mac: four seconds of CPU a day.

By Chethan Kumar S N · Updated

Every daemon in this series gets measured by the same ruler. Processor time, memory, the doors it opens, the words in its manual. remoted earns its page for a different reason: it is the daemon people meet in the wrong places. In the firewall’s allow list, with no memory of putting it there. In a crash dialog that says a problem occurred. In a log search that returns twenty thousand lines overnight. None of those encounters mean anything is broken. This page is what the thing actually is, measured on a real Mac.

What the manual says

macOS ships remoted with a real manual page, and it is short enough to quote in full. The name line: “remoted, Remote Service Discovery daemon.” The description, two sentences and a warning:

remoted is a daemon that discovers remote devices and services.

There are no configuration options to remoted. Users should not run remoted manually.

The page is dated August 26, 2019, which makes it a teenager by this manual’s standards; the series has met daemons whose docs were last touched in 2005 and 2008. Discovery is the whole stated job. Not connecting, not syncing, not controlling. Finding out what is on the other end of a link and telling everyone else.

Six daemons with remote in the name

Before anything else, the name trap. A Mac runs at least six launch jobs with “remote” in the label, and search results mix them constantly:

JobWhat it actually is
com.apple.remotedThis page. Remote Service Discovery.
com.apple.mediaremotedSupport process for the MediaRemote framework, media playback plumbing
com.apple.remotemanagementdMDM, device management for Macs owned by an organisation
com.apple.remotepairtoolPairing helper for remote access features
com.apple.RemoteDesktop.PrivilegeProxyPrivilege helper for Apple Remote Desktop
com.apple.xartstorageremotedCrypto-protected storage, nothing to do with networks

mediaremoted is the common mixup, because both names end the same way and both run as root from boot. They are unrelated. If a search brought you here because Activity Monitor showed “mediaremoted”, that is a different daemon with a different job. This page is about the plain one, and the path column settles every doubt: /usr/libexec/remoted, no prefix, no suffix.

The measurements

Same method as the rest of the series, on a MacBook Pro with an M1 Pro, ten cores, macOS 27.0.1, 26 days and 21 hours of uptime:

The launch job’s own state, read from launchctl: it has run once, never exited, and its start reason is recorded as speculative, meaning launchd started it at boot on the expectation it would be needed, which is standard for a daemon other services query.

Who actually talks to it

The manual says “discovers remote devices and services” and stops. The log shows what that means in practice. Over one full day, 20,454 log lines passed through this daemon, and nearly all of them were the same exchange: a client connects, asks for a device, gets an answer, disconnects. The refrain, over and over:

device_get: Unable to find device with type 3 (client="pid/17361")

In 24 hours, clients asked about a “device with type 3” 134 times and “type 2” 42 times. Apple does not document what the type numbers mean anywhere public; the binary just numbers them. On this Mac no such device was connected, so every ask came back empty, and the clients went away and asked again later.

The client list is the interesting part, because it names the consumers:

That is the shape of the daemon: it is not a user feature, it is a switchboard, and developer tools are its public. The traffic is also bursty. That 20,454 line day included an hour with 5,673 lines, when something was enumerating devices, and quiet hours with a dozen. A quiet three hour window this morning produced 39 lines. If remoted ever looks busy, something is actively asking it about hardware.

The USB leg, in the daemon’s own words

The bursty hours leave better evidence than the quiet ones. During device activity yesterday, the daemon logged errors from a module it calls ncm_host:

Unexpected 3rd parent class IOUSBHostinterface
Unsupported interface
ncm-1> No listener for "com.apple.mobile.storage_mounter_proxy.bridge.macOS"
ncm-1> No listener for "com.apple.remote.installcoordination_proxy"

NCM is USB networking, the class of USB interface a Mac uses to talk to an iPhone or iPad as a network device rather than a disk. The strings in the binary name the whole vocabulary: RSDNCMInterface, RSDRemoteNCMDevice, AppleUSBDeviceNCMPrivateEthernetInterface, and lines like “NCM interface not ready” and “Enable watchdog on ncm-host”. There is even an internal string about treating an NCM host as trusted on a research VM, a leftover from Apple’s own test benches.

Read the error lines as a health report, not a fault. “No listener” means a device was offering a service this Mac had no taker for. Nothing here was broken; the daemon catalogued what arrived, found no local consumer, and moved on.

Six doors, one of them named watchdog

The launch job registers six Mach services, and they read like a map of who the switchboard serves:

Mach serviceReads as
com.apple.remotedThe front door, general queries
com.apple.remoted.coredeviceXcode’s device lane
com.apple.remoted.controlDevice control traffic
com.apple.remoted.virtualizationVirtual machine bridges
com.apple.remoted.compute-platformCompute offload, with its own event feed
com.apple.remoted.watchdogA private liveness check, not the system watchdog

That last row earns a paragraph, because this series met the word before. The system wide watchdog daemon, watchdogd, holds the hardware timer that can restart a hung Mac. Many daemons also reserve a small private watchdog service for themselves, a per-daemon arrangement between a service and launchd. configd has one, WindowServer has one, and remoted has one. They are unrelated to the one with root privileges to panic the machine, which is exactly the distinction the watchdogd page draws.

Why remoted is in your firewall list

This is the question that brings most people here, and it has a concrete answer. The application firewall on macOS keeps a list of applications allowed to take incoming connections. On the Mac measured here, with the firewall enabled, listing that list shows:

8 : /usr/libexec/remoted
    (Allow incoming connections)

The entry was not added by anything you installed. The daemon’s own binary explains why it needs the slot: it takes “incoming remoted bonjour connection” on the local network and connections from devices, and it wraps them in TLS before handing them to Remote XPC, Apple’s transport for talking to trusted device services. A process that accepts connections from other machines is precisely what the firewall list is for, and platform signed system daemons get their entries from the system.

What to do about it: nothing. Blocking it does not make you safer, it makes device work fail quietly, and the entry is a property of macOS, not a sign of tampering. If you want to see your own list, the command is read only:

/usr/libexec/ApplicationFirewall/socketfilterfw --listapps

The one thing worth knowing is the path test, same as every daemon in this series. A real remoted always runs from /usr/libexec/remoted. A process with this name running from your home folder, or /tmp, or an app bundle is not this daemon, and that would be worth a much closer look.

“remoted experienced a problem”

The other doorway into this page is a crash dialog, and the honest answer starts with a count: across 26 days of uptime on the measured Mac, ~/Library/Logs/DiagnosticReports holds zero files for remoted. It has never exited. The dialog you saw, if you saw one, is the same generic notice macOS shows for any process that quit badly, and for a daemon with a keep alive job the recovery is automatic. By the time the dialog rendered, launchd had already restarted it.

The launch job does carry one dramatic setting, and it is worth understanding because it looks scarier than it is. PanicOnConsecutiveCrash is set true, with a companion flag scoping it to automation. In plain terms: if remoted crash loops, launchd escalates that to a system level event rather than restarting it forever. The same pattern appears in the watchdogd launcher. It is Apple saying a fault storm in this daemon is a bigger deal than one crash, not a prediction that one is coming.

So the practical triage for a remoted crash report: read whether there are more than one. A single report, hours or days ago, with the Mac otherwise fine, is noise. A stack of them in one evening means whatever was talking to it, a developer tool, a cable, a connected device, is the actual suspect. Unplug the device, update the tool, and the reports should stop. If they do not, that is a case for Apple Support with the reports attached.

What to do about it

Nothing, in the normal case, which is why there is no settings row anywhere in System Settings for this daemon. It runs as root, so Activity Monitor’s default My Processes view filters it out; switch to All Processes and it sits near the bottom, a few megabytes at most. It has no configuration file, no preference domain, and its manual is firm that you should not run it manually, which also means there is nothing to misconfigure.

If you want to watch it work on your own Mac, one read only command shows the same client refrain this page measured:

log show --last 1h --predicate 'process == "remoted"'

Every request line ends with the process id of the client that asked, so the log always names who is driving the daemon, which is more than most processes offer. Kill it with sudo killall remoted and launchd restarts it in under a second, runs counter back to one, nothing gained. Like the rest of the floor this series has measured, from kernel_task to watchdogd, remoted is not a feature you use. It is plumbing other features depend on, it costs four seconds a day, and the correct amount of attention is roughly what you gave it before you searched its name.

Questions

What is remoted on Mac?

It is Apple's Remote Service Discovery daemon, a root system process at /usr/libexec/remoted that has been running since your Mac booted. Its manual, three sentences dated August 2019, says it discovers remote devices and services, that it has no configuration options, and that users should not run it manually. In practice it is the switchboard other parts of the system query when they want to know what devices are attached: on the Mac measured here, Xcode's device service asked it about devices 1,362 times in one day. It costs about four seconds of processor time a day.

Why is remoted in my firewall list?

Because it is one of the processes macOS itself signs off to accept incoming connections. On a Mac with the firewall turned on, listing the firewall's applications shows /usr/libexec/remoted with an allow entry, placed there by the system. The daemon takes connections over Bonjour on the local network and over the USB link to tethered devices, wrapped in TLS, which is exactly the kind of traffic the application firewall exists to gate. It is platform signed system code, and the entry is normal.

macOS says remoted experienced a problem. Is that bad?

A single crash report for a system daemon is usually a nothing. The launcher restarts remoted the instant it exits, and on the Mac measured here it has never exited once in 26 days, with zero crash reports to its name. The setting that would matter is buried in its launch job: if this daemon crash loops, launchd is configured to treat it as a system level emergency. So the practical reading is, one dialog, ignore it; a repeating pattern of remoted crash reports means something is wrong with a connected device or a developer tool, and that is the thing to unplug or update.

Is remoted the same as mediaremoted or remotemanagementd?

No, and the family resemblance causes real confusion. mediaremoted is the support process for the MediaRemote framework, the machinery behind media playback controls. remotemanagementd handles MDM device management. remotepairtool and the Remote Desktop privilege proxy are separate again. Plain remoted, no prefix, is the Remote Service Discovery daemon, and it is only ever about finding devices and services on the other end of a link. The path column in Activity Monitor settles it: this one lives at /usr/libexec/remoted.

Can I quit or disable remoted?

You should not, and there is no supported way to. There is no row in System Settings for it, its manual says it has no configuration options, and its launch job is set to keep it alive, so killing it buys you seconds before launchd starts it again. If it ever looks busy in Activity Monitor, that is a symptom, not the disease: something, usually a developer tool or a connected iPhone or iPad, is driving the traffic, and the daemon's own log names the client process id on every request. Read the log, find the client, act there.

Ready? Buy Ribbon for $15, or read all the guides.