What is assistantd on Mac, and why is it using the network?

Last updated: 2026-07-31

What it is

assistantd is an Apple-provided background daemon that runs on a per-user basis in macOS. Apple’s system manual page describes it briefly as the daemon that enables Siri functionality. Its verified code identifier is com.apple.assistantd, and the system copy is located at /System/Library/PrivateFrameworks/AssistantServices.framework/Versions/A/Support/assistantd.

The process has a broader supporting role than the one-line manual description might suggest. Its LaunchAgent registers interfaces associated with Siri requests, settings, synchronization, location, and com.apple.assistant.dictation. Calling assistantd a support process for Siri and Dictation is therefore reasonable, although Apple has not published a complete breakdown of which related process handles every operation.

Finding assistantd in Activity Monitor does not mean that a Siri session is underway. Background validation, synchronization, metrics, and maintenance work can also cause it to launch or remain active.

Why it talks to the network

Several network triggers are documented. When you make a Siri request that cannot be handled entirely on the device, the Mac connects to Apple’s Siri processing services. Depending on the request, transmitted information may include audio, transcribed text, request data, relevant context, and an approximate location.

Dictation can also use Apple’s servers. Apple advises checking the Keyboard settings to determine whether Dictation for the current device, language, and feature is processed completely on the device. When full on-device processing is not supported, dictated content is sent to Siri servers.

If Siri synchronization through iCloud is enabled, Siri settings, personalization information, and a small sample of requests can pass through Apple’s synchronization services. A separate opt-in setting, Improve Siri & Dictation, allows audio, transcripts, and related request samples to be uploaded for improvement purposes.

The local launchd configuration also assigns assistantd network-dependent validation, daily synchronization, CloudKit synchronization, metrics transmission, and maintenance tasks. Apple has not published the exact remote hosts or payloads for those individual jobs, so those details remain unverified.

Siri may call third-party apps or services and thereby cause additional network requests. However, whether assistantd itself connects directly to a particular third-party endpoint has not been verified and should not be assumed from the request alone.

How much traffic is normal

There is no reliable published process-level traffic baseline for assistantd. Apple does not provide a normal MB range, and no reproducible independent range has been verified. A precise allowance such as “a few megabytes per day” would therefore be guesswork.

The defensible description is qualitative. While idle, assistantd may produce occasional control, synchronization, validation, metrics, or maintenance traffic. During Siri or Dictation work that requires cloud processing, traffic can rise with the length of the spoken input and the content returned. Its closest general comparison is a short voice interaction, not a system update or a media download, but that comparison is not a numeric baseline.

Sustained high-volume traffic deserves measurement rather than an immediate conclusion. Whether some large resource download could be attributed to assistantd has not been verified, so neither the cause nor a normal upper limit can be stated confidently.

Can you turn it off

The practical verdict is to keep assistantd as a system component. Apple does not provide a System Settings switch for disabling the process itself.

If you do not use its main user-facing features, use the supported feature controls instead. For Siri, open Apple menu  > System Settings > Apple Intelligence & Siri; on some systems the section is labeled Siri. Turn Siri off there. For Dictation, open Apple menu  > System Settings > Keyboard > Dictation and turn Dictation off separately.

Disabling these features removes voice or typed Siri, “Hey Siri,” Siri actions in apps, and standard macOS Dictation. It does not guarantee that assistantd will never launch again, because the daemon also has supporting and maintenance responsibilities.

Apple menu  > System Settings > Privacy & Security > Analytics & Improvements > Improve Siri & Dictation controls only the voluntary submission of improvement samples. Turning it off does not disable Siri, Dictation, or network access needed for ordinary cloud processing.

Force-quitting assistantd, unloading its LaunchAgent with launchctl, or blocking it with a firewall is not an Apple-supported way to disable the feature. The full effects are not public, and launchd may restart the process. Blocking it may interfere with Siri requests, Dictation, personalization synchronization, or related maintenance work.

What people get wrong

• “If assistantd is running, my Mac must be continuously recording and uploading microphone audio.” That conclusion does not follow from the process list or a network connection. Synchronization, validation, metrics, and maintenance can start assistantd without an active voice session. Its presence alone does not prove that audio is being captured.

• “Apple receives every Siri and Dictation recording.” This is too broad. Processing depends on the device, language, and feature being used. Apple directs users to Siri and Keyboard settings to see whether the relevant operation is handled on the device. Data is sent to servers when the required on-device processing is not supported.

• “Turning off Improve Siri & Dictation stops Siri network traffic.” That setting has a narrower purpose: it controls voluntary improvement samples that Apple may store and review. Ordinary Siri or Dictation requests that require cloud processing can still connect to Apple after the improvement option is disabled.

• “Turning off Siri also turns off Dictation.” Siri and Dictation have separate switches in macOS. If you want both features disabled, each control must be changed independently.

• “Removing the LaunchAgent or blocking assistantd is a harmless optimization.” There is no reliable basis for that claim. launchd may start the daemon again, while blocking it may disrupt Siri requests, Dictation, personalized synchronization, or maintenance tasks. Apple has not documented the complete impact of forcibly disabling the process.

• “Any executable named assistantd is the same Apple component.” The verified Apple component has the system path shown above and the code identifier com.apple.assistantd. A file with the same name in another location should not be treated as equivalent; its path and signature need separate verification.

Seeing what it actually used

Because no trustworthy MB baseline exists, the next step is to measure assistantd on your own Mac during idle periods and during Siri or Dictation use. Bytetally’s per-process statistics can show how much traffic was attributed to assistantd, giving you a local comparison without assuming that one fixed range applies to every Mac.

Related processes

Common questions