# assistantd, the daemon that listens when you talk to your Mac

> assistantd is the daemon behind Siri and dictation on macOS. Measured live: the keychain strings behind its prompt, the daily job that deletes sampled audio, and five seconds of CPU a day.

Source: https://www.ribbonmac.com/guides/assistantd-mac · Updated 2026-11-16

Type the first letters of *assistantd* into Activity Monitor and autocomplete finishes the job with a question people ask in the thousands every month: *wants to use the login keychain*. That single suggestion is the most honest introduction to this daemon there is, because assistantd is the rare macOS process whose relationship with your keychain is not incidental. It is built in.

assistantd is the machinery behind Siri and dictation on the Mac. It is the process that answers when you say "Hey Siri", when you hold the microphone key and speak, when you press Fn twice and dictate into a text field. It does not do the speech recognition itself and it does not draw the glowing window, but every request passes through it: it captures the audio, hands it to the recognisers, keeps the session state, talks to Apple's servers when the request needs them, and carries the result back to whichever app was listening. When Siri sets a timer and the timer survives a reboot, that state was checkpointed through this daemon.

It is also one of the quietest processes in this series, and one of the strangest to inspect, because almost everything interesting about it is either locked behind privacy walls or written in its own private vocabulary. This page is the same deal as the others in the [daemon series](https://www.ribbonmac.com/guides/why-is-my-mac-running-slow): everything below was measured read only on a real Mac running macOS 27.0.1, build 26A434, a 10 core Apple silicon machine with 27 days of uptime, with nothing installed and no setting changed.

## What Apple says, and what it refuses to name

Apple's user guide introduces Siri plainly. The page titled *Turn on and activate Siri on Mac* opens: "Siri is an intelligent assistant that's built into your Mac to help you get things done." It walks through the Siri pane in System Settings, the microphone key in the function key row, the menu bar item, and "Hey Siri" or just "Siri" as wake words. It notes the dependency that surprises people: "You must be connected to the internet to use Siri."

Nowhere on that page, on the *If Siri on Mac doesn't work as expected* page, or on Apple's Siri and Dictation privacy pages does the word *assistantd* appear. That is not an omission. It is policy. The daemon is plumbing, and Apple documents the tap, not the pipe. The privacy page is the one place Apple gets specific about what happens to what you say, and three of its sentences do more work than any process listing can:

"A history of your Siri and Dictation interactions is stored on your device and may be used to personalise your Siri experience."

"Your audio data is not stored by Apple unless you opt in to Improve Siri and Dictation or Improve Siri & Apple Intelligence."

And, for the requests that need more compute than your Mac can spare: "Private Cloud Compute provides this information securely to your device and does not retain your data."

Keep those in mind, because the daemon's own launch configuration turns out to agree with them, in writing.

## The identity card, measured

On this Mac, assistantd is process ID 1177, parented by launchd at process ID 1, owned by the user `chethankumar`, which is to say it runs as you, not as root. It has been up for the full 27 days of the machine's uptime: `runs = 1`, last exit status "never exited". Its start reason is logged as an xpc event, which means something asked for it, rather than it ticking over on a timer.

The binary is the largest in this series so far:

```
/System/Library/PrivateFrameworks/AssistantServices.framework
    /Versions/A/Support/assistantd
25,455,360 bytes, built 24 September 2026
x86_64 + arm64e + arm64e.x1, platform identifier 26
code signature: com.apple.assistantd, library validation on
```

For comparison, [usernoted](https://www.ribbonmac.com/guides/usernoted-mac), which runs every notification on the machine, is 6.2 megabytes. assistantd is 25.5, four times the size, and it is not even the Siri stack's biggest wheel. It carries dictation session handling, audio session assertions, vocabulary sync, HomeKit coordination and an interface bridge inside one process, which is a lot of surface for a daemon that spends most of its life waiting.

Its cost of living is tiny. Total processor time across 27 days: 2 minutes 25 seconds. That is about five seconds a day, or six thousandths of one per cent of a single core, on a machine with ten of them. Memory sits near 7 megabytes resident and drifts down when idle, which is what `EnablePressuredExit` in its configuration is for: under memory pressure it is allowed to shed footprint rather than hold it.

## A schedule with a shredder in it

The most interesting thing in assistantd's launch configuration is not what starts it. It is what it runs when nobody is looking. Registered alongside its event triggers are two background system tasks, both repeating every 86,400 seconds, which is one day:

```
com.apple.siri.bg_system_task.speech-audio-sampled
    priority: Maintenance
    requires external power
    requires inexpensive network connectivity
    requires user inactivity

com.apple.siri.bg_system_task.speech-audio-sample-delete
    priority: Maintenance
    requires external power
    requires network connectivity
```

Read the second one again. There is a scheduled job, shipped by Apple, whose entire purpose is deleting sampled speech audio, and it runs once a day when the Mac is plugged in and you are not using it. This is the plumbing behind the privacy sentence quoted above, the one about audio not being stored unless you opt in. The daemon is not merely permitted to forget. Forgetting is on its calendar.

The other task uploads a sample of speech audio for quality measurement when the network is cheap and the machine is idle, which is the counterpart of the opt in: if you have Improve Siri and Dictation switched on, this is the machinery that ships the sample. Both jobs refuse to run on battery power, which is a small mercy for laptops and a useful diagnostic: a Mac that never gets plugged in for long will run these rarely.

The rest of the schedule is reactions. assistantd listens for dozens of distributed notifications, and their names read like a feature list read sideways: `com.apple.assistant.sync_homekit_urgent`, `com.apple.voicetrigger.EarlyDetect`, `com.apple.siri.preheat.quiet`, `com.apple.assistant.app_vocabulary`, and a pair for language model updates, `com.apple.siri.uaf.com.apple.siri.understanding.nl.overrides` among them. Nothing here polls. The daemon sleeps until one of these fires.

## The doors it opens

Count the Mach services a daemon advertises and you have counted its responsibilities. assistantd advertises 32. Some samples, grouped by what they imply:

- `com.apple.assistant.dictation`, `com.apple.assistant.audio-session-assertion`: dictation capture and holding the microphone while you speak.
- `com.apple.siri.hearables`: AirPods and other audio devices, which is how Siri follows you from Mac to earbuds.
- `com.apple.assistant.vocabularyupdates`, `com.apple.assistant.sync`: teaching it the names you actually use, and syncing them across devices.
- `com.apple.siri.pommes_search_xpc_service`: on device search of your own content behind a Siri request.
- `com.apple.assistant.crossdevice.election.service`: the "which device answers" vote that happens when your Mac, iPhone and watch are all in earshot.
- `com.apple.assistant.security` and, inside it, `com.apple.assistant.security.service.keychain`: the keychain door, which gets its own section below.

An election service is worth pausing on, because it explains a common confusion. Say "Hey Siri" near a Mac and a phone and only one answers. That is not the devices being polite. A cross device election runs, the device that heard you loudest and clearest wins, and the others stand down. assistantd is the Mac's candidate in that election.

## The vocabulary is on disk, and it is charming

Every daemon in this series ships its working vocabulary next to its binary, and assistantd's is the first one that talks back. Inside AssistantServices.framework's Resources sit the loctables, plain property lists of localised strings, and the one named `UIUtterances.loctable` holds the phrases Siri uses to explain itself. The British English edition carries 26 of them, and they include:

```
"Hey Siri, set a 5-minute timer"
"You have a missed call from Aakriti at 10:32."
"You have one reminder for today: Pay electricity bill."
"Hey Siri, what's my update?"
"Just say "%@"
```

Somewhere in Cupertino a reminder about an electricity bill became the canonical example of a reminder, and it has been shipped on every Mac since. The neighbouring files are the rest of the personality: `SiriLanguages.loctable` carries 194 strings covering the languages and dialects Siri speaks, `Interstitials.loctable` holds 36 things to say while thinking, and the Resources directory also contains `PhonemeMaps`, a pair of WAV files for announcing messages, a short CAF for the begin tone, and one named `attending-window-end.wav`, which is the sound of Siri deciding you stopped talking.

The strings are localised into dozens of languages, and they are worth knowing about for one practical reason: if Siri ever says something odd to you in your own language, the exact sentence it said is almost certainly in one of these files, findable with a search, which makes it easier to tell a bug from a feature.

## The state it keeps, and the walls around it

Look at what assistantd holds open and you get an honest map of what it remembers. On this Mac, four files dominate:

- `~/Library/Caches/com.apple.assistantd/Cache.db`, 49 kilobytes of ordinary cache in SQLite form, with its write ahead log beside it.
- `~/Library/HTTPStorages/com.apple.assistantd/`, a 4 kilobyte HTTP storage database, the standard per app cookie and cache jar.
- `~/Library/Group Containers/group.com.apple.siri.referenceResolution/Assistant/SiriReferenceResolution/rr.sqlite3`, 12 kilobytes. Reference resolution is how "text her back" becomes a specific contact: pronouns and short names get resolved against a small private database, and this is it.
- The Spotlight sources it reads: CardDAV, LDAP, Exchange, DirectoryServices and a local source, each a small bundle loaded to answer questions about people.

That last item is the sleeper. When you ask Siri to call someone and it knows who, it is not because your contacts were uploaded anywhere. The daemon loads the same contact sources Mail and Calendar use, on the device, and resolves names against them locally. The 12 kilobyte reference resolution database could not hold your contacts if it wanted to. It holds pointers and pronouns, not people.

The walls are real too. The unified log for this process is the quietest in the series: measured over six undisturbed hours, assistantd wrote zero log lines. Not few. Zero. When it does log, the entries are session state and errors, not transcripts, and the audio itself never appears in any file you can read. The privacy page's "stored on your device" is enforced by architecture: the interesting databases are small, local, and unreadable to other processes.

## The keychain prompt, explained properly

Here is what separates assistantd from [usernoted](https://www.ribbonmac.com/guides/usernoted-mac), the other daemon that gets named in a keychain prompt. usernoted's binary contains no keychain code at all; when it triggers a prompt, it is carrying an app's request. assistantd is the app. Its binary contains 51 keychain references, and they are not boilerplate. Read as a list, they describe a deliberate design:

```
com.apple.assistant.security.service.keychain
-[ADMultiUserService _saveDeviceOwnerToKeychainCache]
"Saving Device Owner's sharedUserIdentifier to keychain cache"
"Reading checkpointed state from Keychain"
"Checkpoint state keychain entry does not exist; will use local seed if needed"
"Checkpointing to Keychain"
"Keychain sync incomplete (%@)"
"Shared user identifier changed, triggering keychain sync"
```

The picture those strings paint: assistantd stores a checkpoint of its session state and an identifier for the device owner in your login keychain, and it mirrors Siri related preferences through CloudKit, a job it logs as keychain sync. The keychain, in Apple's own developer documentation, exists to "securely store small chunks of data on behalf of the user", and that is precisely this usage: small, sensitive, per user.

So when the prompt appears and asks, in macOS's exact phrasing, whether assistantd wants to use the login keychain, it is almost always one of three situations. The benign one is first use or a return from a locked keychain: the daemon needs its checkpoint, the keychain wants permission, and Always Allow ends the question for good. The second is after your account password was reset in a way that left the login keychain locked with the old password, which is the classic loop: every process that touches the keychain prompts, assistantd among them, and the fix is Keychain Access, the login keychain's Change Password, and the current account password. The third is an item whose access control list lost an entry, which usernoted's page covers, and which is fixed by re adding the account in the app that owns the item.

What the prompt never means, despite the autocomplete's grim suggestion, is malware. A program pretending to be assistantd would have to be running from outside the system volume with a parent that is not launchd, and both of those are visible in Activity Monitor's Info window in two clicks. The measured process here is 25.5 megabytes of Apple signed, library validated code whose parent is process ID 1.

## The Siri neighbourhood

assistantd works alone the way a conductor works alone. The rest of the ensemble, measured on the same machine:

- **corespeechd**, two copies, one as the system and one as you. This is the actual listener: it watches the microphone stream for "Hey Siri" and wakes the rest when it hears it.
- **siriinferenced**, the on device intelligence that personalises suggestions from your patterns.
- **siriknowledged**, at 24 megabytes resident, actually outweighing assistantd. It maintains the knowledge index Siri answers from.
- **assistant_service**, the sibling binary in the same framework, woken when speech capture finishes, carrying the execution services that run a Siri request to completion.
- **Siri AI.app**, the visible app in macOS 27, which is the face, not the engine.

And one more, which explains a mystery people post about: two *additional* assistantd processes can appear in Activity Monitor, owned by you, with paths deep inside `iPhoneOS.SimulatorRuntime`. Those are Xcode simulator runtimes shipping their own AssistantServices, and their assistantd runs while a simulator is booted. Searching the name finds three and it looks like an infestation. It is two iPhones in software, each with a Siri.

## Is it a virus, and can you quit it

Not a virus: covered above, with the two click check. As for quitting, the honest answer is that there is nothing to gain. Kill it and launchd's event triggers simply start it again at the next Siri or dictation event, and in the gap, dictation buttons and voice activation are dead. There is no KeepAlive forcing it to run constantly, and it does not need one, because the Mac asks for it the moment you speak.

If your actual goal is less Siri, the settings are the lever. The Siri pane turns Siri off entirely. Keyboard settings, Dictation, turns off dictation. And in the Siri pane, under Improve Siri and Dictation, there is a delete option for the interaction history stored on your device, which is the human face of the deletion job the daemon already schedules nightly.

## Where window managers fit

Nothing in assistantd's workload touches windows, and a window manager cannot touch it back. The only honest connection is the one this series always finds: a busy Mac is a busy Mac, and knowing which process is which, [kernel_task](https://www.ribbonmac.com/guides/what-is-kernel-task-on-mac) when it is hot, [WindowServer](https://www.ribbonmac.com/guides/what-is-windowserver-on-mac) when it is redrawing, assistantd when it is listening, is how you stop fixing the wrong thing. Ribbon arranges windows as a scrolling strip so the arranging itself stays out of the CPU column. It is $15, once, for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs.

## The short version

assistantd is Siri and dictation's daemon: started at login, running as you, woken by events rather than timers, cheap at five seconds of processor time a day. Its launch configuration schedules a daily deletion job for sampled speech audio, which is Apple's audio privacy promise expressed as a cron entry. It stores a session checkpoint and a device owner identifier in your login keychain by design, which is why the keychain prompt names it, and a looping prompt means a locked or mismatched login keychain, not an intruder. It is the biggest binary in this series and the quietest log, and if you see three of them, two belong to iPhone simulators.

## How to look at your own

All of this is readable on any Mac, read only, in a terminal:

```
ps -Awwo pid,ppid,user,%cpu,rss,etime,args | grep "[/]assistantd"
launchctl print gui/$(id -u)/com.apple.assistantd | head -40
plutil -p /System/Library/LaunchAgents/com.apple.assistantd.plist
strings -a /System/Library/PrivateFrameworks/AssistantServices.framework/Versions/A/Support/assistantd | grep -i keychain | head
log show --last 1h --predicate 'process == "assistantd"'
```

The `ps` line shows the parent and owner, which is the virus check. The `launchctl` line shows runs and exit state. The `plutil` line shows the daily delete job in full. The `strings` line shows the keychain design in 51 lines. And the `log` line, on an idle Mac, will most likely show you nothing at all, which, for a daemon that hears everything you say to your computer, is exactly what you want it to show.

## FAQ

### What is assistantd on Mac?

It is the daemon that powers Siri and dictation. When you say Hey Siri, hold the microphone key and speak, or press a key and dictate anywhere you could type, assistantd is the process behind it: it captures the request, decides which piece handles it, talks to the speech recognition machinery, and carries the answer or the dictated text back to the app. It lives at /System/Library/PrivateFrameworks/AssistantServices.framework/Versions/A/Support/assistantd, it is started by launchd the moment you log in, and it runs as your own user account rather than root. On the Mac measured here it has been alive for 27 days without a single restart, has used about five seconds of processor time a day, and holds about 7 megabytes of memory. Apple's own documentation describes everything Siri does without once naming this process.

### Why does assistantd want to use the login keychain?

Because storing and syncing some of its state in the keychain is part of its design, unlike most daemons that never touch it. The binary measured here contains 51 keychain references, including a service literally named com.apple.assistant.security.service.keychain and log lines such as Reading checkpointed state from Keychain and Checkpointing to Keychain. It keeps checkpoint state and a device owner identifier there, and mirrors Siri preferences through CloudKit in a process its own strings call keychain sync. When the keychain is locked or an item's access list needs reapproval, macOS names the process doing the reading, so the prompt says assistantd. Clicking Always Allow ends it when the keychain is healthy. If it returns in a loop, the usual cause is a login keychain password that no longer matches your account password, which happens after an account password reset done outside System Settings, and the durable fix is opening Keychain Access, selecting the login keychain, and changing its password back to the current account password.

### Is assistantd a virus or malware?

No. It is Apple's own code, signed with identifier com.apple.assistantd and platform identifier 26, built in September 2026, sitting on the sealed system volume where nothing can quietly modify it. It is normal for it to be running: its launch configuration starts it at login and it stayed up for 27 days on the Mac measured here. The search phrase assistantd mac virus is common enough that autocomplete suggests it, which says more about how unfamiliar the name is than about the process. The check that matters is identity, not the name: anything calling itself assistantd but running from your home folder, Downloads, or an app bundle you downloaded, or whose parent is not launchd, would be worth a closer look. The real one's parent is process ID 1 and its path is inside AssistantServices.framework.

### Why does assistantd show more than one process, or use memory and CPU?

If you search for it in Activity Monitor you may see three rows with that name and only one is the real system daemon. The others come from iOS simulator runtimes: Xcode's simulators ship their own copies inside AssistantServices.framework, and when a simulator is booted its assistantd runs too. They belong to the simulator, they die with it, and they explain a duplicate that is not duplication. The system copy itself is cheap: measured across 27 days of uptime on a 10 core MacBook Pro it had used 2 minutes 25 seconds of processor time in total, about five seconds a day, and its memory sat around 7 megabytes, which is small for a daemon whose binary is 25.5 megabytes. Bursts of CPU line up with dictation and Siri sessions, not with idle time: in six undisturbed hours its unified log wrote zero lines.

### Can I quit or disable assistantd?

You can kill it, but there is no reason to and it undoes nothing you care about. Its launch configuration registers dozens of event triggers, so launchd starts it again on the next Siri or dictation event, and features that route through it, including Type to Siri, voice activation, and every app's dictation button, stop working until it comes back. The lever you actually have is in System Settings. Siri can be turned off entirely in the Siri pane, and dictation can be turned off in Keyboard settings under Dictation, both of which remove the occasions that wake the daemon. There is also a privacy reset worth knowing about: in the Siri pane, Improve Siri and Dictation has an option to delete the interactions history that is stored on your device, which is the human facing version of the cleanup job the daemon already schedules for itself every day.
