HeartbeatHocusFocusFilesMacHyperTile
Guide

suggestd, the daemon that learns what to suggest

suggestd is the Mac daemon behind Siri Suggestions. Measured live: its sixteen scheduled jobs, the portrait it keeps of you, and what its CPU should cost.

By Chethan Kumar S N · Updated

Of all the lowercase daemons in Activity Monitor, suggestd has the least mysterious name in the list. Suggest, plus d for daemon. The entire job description is the word before the suffix: this is the process that suggests. When Spotlight offers the app you wanted before you finish typing its name, when QuickType slides the right word under your thumb, when the Lock Screen quietly mentions the meeting you would have forgotten, the guessing engine behind it is this one process, running as you, reading what flows through your own apps.

People rarely meet it on purpose. They meet it at the top of a CPU column during a warm evening, or in a password dialog that says suggestd wants to make changes, and then they search for it. What they find is usually three years of forum threads with no measurements in them. This page has measurements. It was built the way the other process pages in this series are built, from the daemon’s own manual entry, its own launch configuration, its own framework, its own logs and its own files on disk, measured read only on one Mac running macOS 27.0.1 on Apple silicon. Every command is at the end if you want to repeat any of it.

The manual page, all 402 bytes of it

suggestd ships with its own manual page, suggestd(8), which puts it in a small club alongside WindowServer, netbiosd and routined. It is 402 bytes long, dated 26 June 2017, and it says:

NAME
     suggestd - daemon that processes user content in order to detect
     contacts, events, named entities, etc.

DESCRIPTION
     suggestd The suggestd daemon receives content from Spotlight, Mail,
     Messages and various other apps in order to power various features.
     Those features include Found in Apps, Proactive QuickType, and
     Keyboard/Siri/News Personalization.

Two sentences of description, and they hold up nine years and ten major OS versions later. The first names the inputs: your content, arriving from Spotlight, Mail, Messages and various other apps. The second names the outputs: Found in Apps, the feature that tells you where you saw a thing; Proactive QuickType, the keyboard that predicts; and Keyboard, Siri and News personalization. Between the inputs and the outputs sits the entire modern suggestions stack, described in 2017 by someone who either wrote it or understood it deeply.

It runs as you, from the smallest binary in this series

$ ps -Awwo pid,ppid,user,%cpu,rss,etime,time,args | grep "[/]suggestd"
79892     1 chethankumar    0.0  42976  3-01:19:39   1:04.48 /System/Library/PrivateFrameworks/CoreSuggestions.framework/Versions/A/Support/suggestd

Parent process 1 means launchd started it. The user column says it runs as your own account, not root, because the content it processes belongs to you. The path runs through CoreSuggestions.framework, Apple’s private framework for exactly this job, in the Support folder next to the code that calls it.

The binary itself is 435,600 bytes, the smallest in this series so far, smaller even than logd’s 628 KB. It is a universal binary with slices for x86_64, arm64e and arm64e.x1, marked Platform 26, signed by Apple in September 2026, and it contains only 538 strings. That thinness is a clue, not a shortage: the machinery lives in the framework around it, and the daemon is the mailbox. Its launch configuration hands it two environment settings that say a lot, MallocSpaceEfficient set to 1, because a daemon that lives forever should not hoard memory, and OSLogRateLimit 64, so a chatty framework cannot flood the unified log.

A life of planned naps

Most daemons in this series either never exit or work shifts. suggestd does something different: it naps on purpose. The launch configuration sets EnablePressuredExit, which gives macOS permission to reclaim its memory when the system is under pressure, and the accounting shows the system taking that permission:

$ launchctl print gui/$(id -u)/com.apple.suggestd | grep -E "runs|last exit|immediate"
	runs = 3
	last exit reason = JETSAM_REASON_MEMORY_IDLE_EXIT
	immediate reason = ipc (mach)

Three runs in the Mac’s uptime. The last exit was JETSAM_REASON_MEMORY_IDLE_EXIT: the system ejected an idle process to have its memory back, on purpose, the same polite eviction contactsd gets. And the immediate reason for the current run is a mach message, meaning something asked for it and launchd woke it up. The throttle interval is three seconds, the minimum runtime three seconds, the exit timeout five. This is a daemon designed to be woken, used, and put away.

The mailroom: fourteen inboxes

What does a suggestions daemon need to be woken for? Its configuration answers with Mach services, the named doors other processes knock on, and fourteen of the thirty-eight are per-app inboxes:

com.apple.suggestd.contacts
com.apple.suggestd.deliveries
com.apple.suggestd.events
com.apple.suggestd.fides
com.apple.suggestd.ipsos
com.apple.suggestd.mail
com.apple.suggestd.mail-intelligence
com.apple.suggestd.messages
com.apple.suggestd.reminders
com.apple.suggestd.spotlightknowledged
com.apple.suggestd.urls

Contacts, deliveries, events, mail, mail intelligence, messages, reminders, URLs. The manual page said it receives content from Spotlight, Mail, Messages and various other apps; here is that sentence rendered as plumbing. When Mail finishes indexing a message, something knocks on the mail door. When you add a reminder, the reminders door. There is even a notifyd trigger named com.apple.suggestions.prepareForQuery, which is the system telling the daemon to warm up because a suggestion is about to be requested. ipsos is survey tooling, and fides, Latin for faith or trust, is privacy enforcement. Apple named a privacy service in a dead language, which tells you how old some of this stack is.

The portrait: sixteen services that describe you

The other big family of Mach services is the point of the whole machine. Sixteen services, all beginning com.apple.proactive.PersonalizationPortrait:

PersonalizationPortrait.Contact
PersonalizationPortrait.Event
PersonalizationPortrait.Location.readOnly
PersonalizationPortrait.Location.readWrite
PersonalizationPortrait.NamedEntity.readOnly
PersonalizationPortrait.NamedEntity.readWrite
PersonalizationPortrait.Topic.readOnly
PersonalizationPortrait.Topic.readWrite
PersonalizationPortrait.QuickType
PersonalizationPortrait.SocialHighlight
PersonalizationPortrait.TemporalCluster
PersonalizationPortrait.TextUnderstanding
PersonalizationPortrait.Connections
PersonalizationPortrait.Config

Read the nouns and you have the data model of a person: contacts, events, locations, named entities, topics, connections between them, clusters of things that happened near in time. A read only and a read write variant for the sensitive ones, so a client can be granted looking without touching. This is the portrait the man page’s 2017 description implies, and it is not a metaphor. It is a schema, with a service per table.

The portrait is stored on disk, in your own Library, in two directories named for the job: ~/Library/Suggestions and ~/Library/PersonalizationPortrait. Both exist on the measured Mac, and both are guarded, because even your own account cannot read into them without Full Disk Access. Listing the contents returns Operation not permitted. That wall is worth knowing about, in both directions: nobody’s sketchy menu bar app is casually reading your suggestion history, and you cannot audit yours either without granting a tool the very access you are trying to inspect.

The framework ships its vocabulary too. Its Localizable file carries eleven strings in each of forty-four locales, and they read like captions for the portrait:

Found in %@ with %@
Chatting with %@
You interacted with %@ using %@, %@
Maybe: %@
Recent Call
%@: Check-in

Found in Mail with a name. Chatting with a name. The Maybe prefix, hedging an uncertain extraction the way a careful person would. Beside those sit TimeZoneAirportCodes, TimeZoneCountryNames and TimeZoneRegionAbbreviations, because an event suggestion is only useful with the right timezone, and a Ragel grammar file, the actual state machine that parses text as it is harvested.

Sixteen jobs, and most refuse to run on battery

The schedule is where a suggestions daemon earns its reputation, so it is worth reading in full. The launch configuration registers sixteen repeating background jobs with launchd’s activity system:

com.apple.proactive.ProactiveHarvesting.Harvest.PeriodicBackground  every 8h   CPU intensive, no battery
com.apple.proactive.ProactiveHarvesting.Cleanup                     every 24h  no battery
com.apple.suggestd.identityanalysis                                 every 24h  CPU intensive, no battery
com.apple.suggestd.cd-cache-rebuild                                 every 24h  CPU intensive, no battery
com.apple.suggestions.sqlentitystore.cacheprecomputation            every 24h  CPU intensive, no battery
com.apple.suggestd.vacuum                                           every 24h  no battery
com.apple.suggestd.trim                                             every 48h  no battery
com.apple.suggestd.mail-intelligence-tasks                          every 24h  no battery
com.apple.suggestd.ma-metadata-download                             every 24h  no battery
com.apple.suggestd.process-pending-geocodes                         every 24h  no battery
com.apple.suggestd.process-pending-verification                     every 24h  no battery
com.apple.suggestd.harvested-url-metric-upload                      every 24h  no battery
com.apple.suggestd.sendrtc                                          every 24h  no battery
com.apple.suggestd.phone-qr-engagement-data-recording               once
com.apple.suggestd.analytics-heartbeat                              every 3h   battery allowed
com.apple.suggestions.collectweeklystats                            every 168h  no battery

A harvest every eight hours, marked CPU intensive, plus a daily cleanup, a daily identity analysis, a daily cache rebuild, a daily vacuum and a trim every two days, like groundskeeping for a database. Every job on the list except the three hourly heartbeat carries AllowBattery false, and most also opt into PowerNap, which means the Mac can do this work while the lid is closed and the machine is plugged in. If you have ever noticed a sleeping Mac’s fans spin up briefly while charging, jobs like these are the kind of thing that happens.

The names answer the questions people actually search for. High CPU on suggestd is almost always the eight hour harvest or the daily cache rebuild, not a malfunction. The word vacuum appears because there is a database, and databases need vacuuming. And process-pending-geocodes exists because an event suggestion without a place is just a string.

The gate, watched live

The configuration says the jobs are power gated. The logs show the gate working. In thirty minutes of captured output, 809 lines, the daemon checked its own throttle and reported:

(ProactiveHarvesting) Throttle check: 500 ops left (HVPowerBudgetLevelFull),
    connectedToPower 0, disabled 0, canProcess HVPowerBudgetLevelFull
(ProactiveHarvesting) Budget Status Changed to "Have discretionary budget"
    from "Connected to Power" after 5491 seconds

Five hundred operations of budget, the power level reported full, and a transition from connected to discretionary after five thousand four hundred and ninety one seconds, which is the scheduler demoting work from run now to run when idle. This is what a well behaved background system looks like from inside: it counts what it is allowed to do before it does it.

The rest of the half hour is quieter. Every five to ten minutes a connection status change arrives from apsd, the push daemon, and suggestd checks whether it has a delegate that cares. And once, a real job: a contact lookup, one identifier, nine keys fetched, avatars considered, wallpaper key not needed, finished in 47 milliseconds. That single fetch is the whole machine in miniature. A suggestion needed a person, so the daemon asked Contacts, got an answer, and went back to sleep. On the measured Mac, that pace adds up to one minute and four seconds of processor time over three days, about twenty one seconds a day, which sits between routined’s sixteen seconds and contactsd’s thirty one in this series’ ledger. The heaviest quiet daemon measured so far remains logd, at nine minutes a day, twenty six times this one.

No crashes, and the matter of the third suggestd

Both DiagnosticReports folders on the measured Mac, the user’s and the system’s, hold zero crash reports for suggestd. The quit unexpectedly searches that lead people here usually have the same answer the routined page found: simulators. This Mac was running three suggestd processes at measurement time. The real one, parent 1, launched by launchd. And two whose full paths run through the simulator runtimes, one for iOS 27.0 and one for iOS 27.1, children of CoreSimulator processes, living inside cryptex mounts. A simulated iPhone needs its own suggestions daemon, because iOS ships one too, and it is the same code built for the other platform. Those copies are harmless, small, and die with the simulator. If your copy is crashing and its parent is not 1, you are probably debugging someone else’s operating system.

What Apple says, and does not say

The full table of contents of the macOS User Guide for this version, a quarter of a megabyte of page listings, contains the word suggestd zero times. Apple describes the feature and never the machinery, which is consistent policy: the same guide never names mds_stores, logd or any daemon in this series. What it does say is quotable. The Customise Siri page: when Suggestions are on, you get suggested actions even before you ask. Suggestions can appear in apps, Search or in widgets. They are on by default, but you can turn them off at any time. Click Suggestions, then turn them on or off for each app. And for the nuclear option: excluded apps are not available to Siri, Search or suggestions.

So the off switches are real, per app, and they live in the Siri settings pane. What they turn off is the feature, the appearing of suggestions. The process stays, because it is also the mailroom for QuickType and the reader for Spotlight knowledge, and because launchd does not retire plumbing just because a tap was closed.

One job, four daemons, no overlap

This daemon is easy to confuse with its neighbours, so here is the map. Spotlight indexing is mds and mds_stores: they build the index of your files so search can answer instantly. suggestd builds the meaning on top: what you are likely to want, given what you have been doing. routined learns where you go and predicts visits. contactsd serves the address book itself, and suggestd is one of its clients, as the 47 millisecond fetch in its logs proves. Index, meaning, place, people. Four daemons, four nouns, and the guessing engine in the middle is this one.

A daemon that reads your mail and messages on device, keeps a portrait of you in two walled directories, works eight hour shifts only while plugged in, counts its own operations against a 500 op budget, costs twenty one seconds a day, and has never crashed once. It is the most personal daemon in this series, and also among the best behaved.

See for yourself

Every claim above came from commands like these, all read only:

$ ps -Awwo pid,ppid,user,%cpu,rss,etime,time,args | grep "[/]suggestd"
$ man suggestd
$ plutil -p /System/Library/LaunchAgents/com.apple.suggestd.plist
$ launchctl print gui/$(id -u)/com.apple.suggestd | grep -E "runs|last exit|immediate"
$ ls -l /System/Library/PrivateFrameworks/CoreSuggestions.framework/Versions/A/Support/
$ codesign -dv /System/Library/PrivateFrameworks/CoreSuggestions.framework/Versions/A/Support/suggestd
$ ls /System/Library/PrivateFrameworks/CoreSuggestions.framework/Versions/A/Resources/
$ ls ~/Library/Suggestions ~/Library/PersonalizationPortrait
$ log show --last 30m --predicate 'process == "suggestd"' --style compact
$ ls ~/Library/Logs/DiagnosticReports/ /Library/Logs/DiagnosticReports/ | grep -i suggestd

The plist is the interesting one. Sixteen named jobs with their power rules, thirty-eight Mach services with their nouns, printed in a second, no tools installed.

Questions

What is suggestd on Mac?

It is the daemon that powers Siri Suggestions. Its own manual page, unchanged since June 2017, describes it as a daemon that processes user content in order to detect contacts, events, named entities, and says it receives content from Spotlight, Mail, Messages and various other apps to power features including Found in Apps, Proactive QuickType, and Keyboard, Siri and News personalization. In plain terms: when Spotlight guesses the app you want before you finish typing, when QuickType offers the word you were about to tap, when Mail offers the contact you were about to look up, this is the process behind it. It runs as your own user account, not root, it lives inside the CoreSuggestions framework, and on the Mac measured here it costs about twenty-one seconds of processor time a day.

Why is suggestd using so much CPU?

Because one of its sixteen scheduled jobs fired. The heaviest is called ProactiveHarvesting.Harvest.PeriodicBackground: it runs every eight hours, is marked CPU intensive in the daemon's own configuration, and refuses to run on battery. Three more daily jobs carry the same marks, including one called identityanalysis and one that rebuilds a cache. A burst usually means a lot of new mail arrived, or the Mac was upgraded and the learning is being redone, or the machine was finally plugged in and the backlog ran. The configuration gates all of it on power: in thirty minutes of its logs on the measured Mac, the daemon reported a budget of 500 operations, full power budget, and noted it had discretionary budget again after 5,491 seconds. Sustained high CPU for hours on a quiet, powered Mac would be unusual; the measured cost here was twenty-one seconds a day.

A dialog says suggestd wants to make changes. What is it asking for?

That dialog names the process that triggered it, and suggestd is Apple's own platform code: it is signed by Apple, marked Platform 26, and lives in a system framework, which you can verify with the commands at the end of this page. The daemon has a legitimate reason to touch protected data. Its logs show it reading contacts directly, it ships a Mach service named suggestd.contacts, and its configuration listens for a notification literally called suggestions.settingsChanged, which fires when permissions move. On the Mac measured here it never asked for anything, because it was already authorized. The rule that matters: never type a password into a dialog for a process whose path you have not checked. If the path starts with /System/Library, it is the real one.

Why are there three suggestd processes on my Mac?

Almost certainly because Xcode simulators are running. On the Mac measured here there were three: one at parent process 1, which is the real one launchd started, and two more whose paths ran through com.apple.security.cryptexd and iPhoneOS SimulatorRuntime, one for an iOS 27.0 runtime and one for 27.1. Those two belong to pretend phones. They are the same daemon built for iOS, doing the same job inside a simulated device, and they stop when the simulator does. If you have never installed Xcode, there should be exactly one, and the parent should be 1.

How do I turn Siri Suggestions off, and does that stop suggestd?

The switches live in the Siri settings pane. Apple's own Customise Siri page, which never names suggestd once, states the terms: when Suggestions are on, you get suggested actions even before you ask, they can appear in apps, Search or in widgets, they are on by default, and you can click Suggestions, then turn them off for each app. There is also an exclusion list, and Apple says excluded apps are not available to Siri, Search or suggestions. Turning the switches off stops the feature. The process itself is plumbing, and launchd will keep it resident, because the same daemon also serves the QuickType keyboard and other callers that stay on.

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