chronod, the daemon that keeps your widgets on time
It is the daemon that refreshes widgets and forwards live activities, ten seconds of CPU a day, one run in 29 days, and a log that names every widget it serves. Measured on a 29 day Mac.
By Chethan Kumar S N · Updated
The weather widget on your desktop changed itself just now. It did not ask the Weather app, and it did not ask you. Something decided, to the second, that this was the moment to fetch a new timeline of conditions and repaint a small rounded rectangle, and something had to be awake to make that decision while everything else slept.
That something is chronod, and it is one of the busiest quiet processes on a modern Mac. Its own log, over one unremarkable hour on the machine measured here, runs to 1,790 lines, almost all of them scheduling, launching and tidying up after widgets. Its processor bill for 29 days of that work: five minutes and five seconds. This page is the measurement, all of it read off a Mac running macOS 27.0.1, nothing installed, nothing written.
A daemon with no documentation at all
Start with the honest hole in the record, because it is bigger than usual. chronod has no manual page: man chronod returns no manual entry for chronod, in a system that still ships manual pages for daemons from 2011. Apple’s developer documentation for WidgetKit, the public framework on the other side of this machinery, opens with a single sentence that names the territory and never the plumbing: “Extend the reach of your app by creating widgets, watch complications, Live Activities, and controls.” The Mac User Guide’s page for adding widgets, Add and customise widgets, walks through the gallery, the desktop, Notification Centre and the Use iPhone widgets switch without once naming the process that would do the refreshing. A search of every page fetched for this piece turned up zero mentions.
That is why this name lives in Activity Monitor and in search rows rather than in Apple’s prose. The most specific things people ask are what is chronod on my mac, what is chronod macbook, what is chronod process, and a small anxious family around chronod macos high cpu and chronod 100 cpu. All of them are questions about a process Apple has never introduced.
The name decodes to a project called Chrono
The binary lives at:
/System/Library/PrivateFrameworks/ChronoCore.framework/Support/chronod
243,728 bytes, universal for Intel and Apple silicon, signed with the standard first party ladder. The framework’s own version file answers the question the missing manual page does not: ProjectName Chrono, BuildVersion 483. Inside Apple, this is the Chrono stack.
And it is a stack. Sitting beside ChronoCore on every Mac are ChronoKit, ChronoServices, ChronoUIServices, DistributedTimers, DistributedTimersDaemon, IdleTimerServices, MobileTimer, MobileTimerSupport, MobileTimerUISupport, SiriTimeTimerInternal and TimerAppIntents. Read that list as a job description: distributed timers, mobile timers, Siri timers, timer app intents. This is the machinery that makes a timer started on one device ring on the others, and the machinery that decides when a widget’s future is due.
The launch file adds one more word to the decode. chronod is not a LaunchDaemon at all. It is a LaunchAgent, /System/Library/LaunchAgents/com.apple.chronod.plist, restricted to the Aqua session, which is to say your desktop and only your desktop. It runs as you, not root. It is a member of your login session that happens to be written by Apple, in the same convention breaking family as the Accessibility server this series has already measured.
It writes its own wake up call
The launchd report for the job is short and strange in one specific way:
state = running
runs = 1
last exit code = (never exited)
immediate reason = xpc event
minimum runtime = 3
exit timeout = 5
One run, 29 days, no restarts, started on an XPC event and kept alive by nothing except its own usefulness: RunAtLoad is false, KeepAlive is set only for crashes, and a ThrottleInterval of 3 seconds is the only opinion launchd holds about its restarts.
The strange part is further down, in the event triggers:
com.apple.chronod.nextScheduledTimelineRefresh => {
stream = com.apple.xpc.activity
monitor = com.apple.UserEventAgent-Aqua
descriptor = {
"Repeating" => false
"Interval" => 1549
"Delay" => 1539
"GracePeriod" => 10
"Priority" => "Utility"
}
}
Read that as an appointment book. Every time chronod finishes refreshing a timeline, it books the next one: a non repeating XPC activity, 1,549 seconds out, watched on its behalf by the user event agent. The daemon is both the client and the thing being woken. Its log says so in plain English at least twice an hour, in lines like Scheduling waking task for adjusted date and Scheduling waking work for, followed by a date. cron, still sitting unused at /usr/sbin, polls a clock. chronod books a wake up call and hands it to launchd, which is the whole difference between the old scheduler and the new one, caught in one plist key.
Twenty five ways to be woken
The rest of its launch file is a list of everything that can interrupt a nap, and it reads like a summary of what the daemon worries about. An app being installed, changed or uninstalled, three separate LaunchServices events. A focus configuration change, watched through do not disturb. A permission event, watched through tccd. A per app language change. Keybag lock status, the moment your encryption keys go in or out of the hardware. The significant time change notification, the one that fires when the clock jumps, across a time zone or a daylight saving boundary.
Then ten accessibility events: bold text, differentiate without colour, increased contrast, invert colours, preferred content size, reduce motion, reduce transparency, each one a notification chronod listens for because widget and live activity rendering has to follow the shape of your screen settings. A daemon that keeps time for things you look at has to re render them when you change how you look.
And one pair that names its partner: com.apple.chronod.replicator.message and com.apple.chronod.replicator.record, plus a watch on com.apple.replicatord.devicesChanged. This is the iPhone widget lane. replicatord, measured elsewhere in this series, is the courier that copies an iPhone’s widget data to the Mac, and it is woken when the Mac’s radio hears a phone advertising a service literally called com.apple.ApplicationService.chrono. The two daemons are the Mac’s halves of one system, and each one’s launch file names the other.
Five doors, and what comes through them
The doors are the MachServices block, and each one is a client list:
com.apple.aps.chrono.PushNotifications
com.apple.aps.chrono.PushNotifications.dev
com.apple.chrono.controlcenter
com.apple.chrono.widgetcenterconnection
com.apple.chronod.replicator
com.apple.chronoservices
The push pair is how a refresh can arrive from Apple’s servers, an alarm of yours changing on someone else’s machine and reaching yours. The controlcenter door is the timer that sits in the menu bar’s Control Centre. The widget centre connection is the desktop and Notification Centre. The replicator door is the iPhone. chronoservices is everything else that wants a named timer, which on this machine includes the Siri stack.
An hour in the log is a widget census
One quiet hour, 1,790 lines, and the shape of the hour is more interesting than the count. The biggest single category, 141 lines, is runningboard monitor updates, the process supervisor telling chronod which widget extensions are alive. There are wake events, in English: “Wake event received [distnoted]: application-installed”, the moment something got installed and every widget’s availability had to be re checked. That one wake was followed by forty consecutive CFURLResolveBookmarkData operations, the daemon re resolving its notes about what was just installed.
And there, verbatim, is the job description nobody at Apple wrote down:
Add pending task: timeline<com.apple.chronod.timeline-host::
[com.apple.weather::com.apple.weather.widget:com.apple.weather:1289529871828302290]>
...
Reload timeline: com.apple.weather::com.apple.weather.widget
Session operation: `getTimelines(1)` request.
The task names chronod as the timeline host, name the app, the widget and an instance number, and then the WidgetKit session asks for one timeline. That is a weather widget refreshing on a desktop, end to end, and chronod is the host at every step: it queues the reload, launches the extension process to do the drawing, watches the process with RunningBoard in case it dies, and books the next refresh before going back to sleep.
The evidence in its open files
The strongest single proof of what this daemon does is not in its log. It is in the list of files it holds open, because chronod keeps the localised name table of essentially every widget extension on the system: the Clock app’s World Clock widget, Calculator, Calendar, Home, Journal, Notes, Podcasts, Reminders, Shortcuts, Stocks, Tips, Voice Memos, Weather, Batteries, Control Centre’s display controls, the Dock’s controls. A daemon reads those files for one reason: it needs to know every widget by name, in your language, because it is the thing connecting widgets to the places they appear.
The framework ships exactly one human sentence of its own, a localisation file with the single entry “Unknown Source”, and one longer dialog that explains a feature you may meet on a new Mac, quoted here whole: “If you turn off forwarding for an individual app, new apps you install and allow live activities from will not be forwarded to this accessory automatically.” Live activities, the dinner timer and delivery countdowns of the iPhone world, now continue onto accessories near your Mac, and the daemon deciding which app’s live activities may ride along is this one.
What it costs, and who to blame instead
The bill for all of the above, measured over 29 days of uptime: 5 minutes 5 seconds of processor time, call it ten seconds a day, on 45 MB of memory. In the same ps line, its partner replicatord shows 4.9 seconds total. The pair of them, the entire widget and timer scheduling layer of macOS, costs less CPU in a week than one browser tab spends on a page you have already stopped reading.
If Activity Monitor ever shows chronod genuinely busy, the log names the widget responsible, because every task it runs carries the widget’s bundle identifier. The levers are the visible ones: remove or re add the widget it keeps naming, trim the desktop collection, switch off Use iPhone widgets if the phone side is churning, and if you develop for iOS, remember that every booted simulator runs its own chronod next to its own replicatord. The two extra copies on the measured Mac had burned 50 and 25 seconds respectively in three days, more per day than the real one. The clerk is cheap. The number of clerks is on you.
See for yourself
Everything on this page came from read only commands that work on any Mac:
ps -Awwo pid,user,%cpu,rss,etime,comm | grep [c]hronod
launchctl print gui/$(id -u)/com.apple.chronod
plutil -p /System/Library/LaunchAgents/com.apple.chronod.plist
log show --predicate 'process == "chronod"' --last 1h
The launchd report is the one to try. Somewhere in its event triggers, expressed as an interval and a grace period rather than as a sentence, is the exact second your weather widget next refreshes.
Questions
What is chronod on my Mac?
It is the timeline daemon, the process that decides when the widgets on your desktop and in Notification Centre refresh, launches the little extensions that draw them, and forwards live activities to nearby accessories. It lives in the ChronoCore private framework, runs as your own user account rather than root, and it has been running since the moment you logged in. Apple never names it anywhere: it has no manual page and it appears in none of the user guide's widget pages, because it is plumbing. The searches that find this page are its public trail, rows like what is chronod on my mac and what is chronod process, which people type after meeting it in Activity Monitor and finding nothing in Apple's documentation to explain it.
Why is chronod using high CPU?
On its own, almost never. The Mac measured here, on macOS 27.0.1 with 29 days of uptime, showed chronod at 5 minutes 5 seconds of total processor time, about ten seconds a day, at 0 percent in the CPU column while writing 1,790 log lines in a single quiet hour. The work is all sub second: wake, reload one timeline, launch one widget extension, go back to sleep. When this name does run hot, the log says why, because every task it runs is named after the widget it belongs to. A widget stuck in a reload loop, a misbehaving third party widget extension, or a screen full of widgets that each want their own schedule are the usual culprits, and the fix is to remove or re add the widget the log keeps naming, not to fight the daemon.
Why are there multiple chronod processes?
Almost always the iOS Simulator. Every simulator runtime you have booted ships its own copy of the ChronoCore framework inside its RuntimeRoot, and each booted simulator runs its own chronod, plus its own replicatord. The Mac measured here had three: the real one at about 45 MB, and two simulator copies from an iOS 27.0 and an iOS 27.1 runtime, sitting at paths under /private/var/run/com.apple.security.cryptexd. If you are not running the Simulator and see more than one chronod, check the path column in Activity Monitor. The real one lives at /System/Library/PrivateFrameworks/ChronoCore.framework/Support/chronod and nowhere else.
Is chronod a virus or malware?
No. The real binary sits on the sealed system volume at /System/Library/PrivateFrameworks/ChronoCore.framework/Support/chronod, 243,728 bytes, and its code signature chains through macOS Software Signing to Apple Code Signing Certification Authority, the standard ladder for a first party process. It runs as your own account, not root, so it never had the privileges malware wants. There are no virus or malware rows in its search family at all, which fits a process whose scariest symptom is a widget refreshing twice. The honest test is the same as for every daemon in this series: read the path column. A process calling itself chronod from a downloads folder would be a costume.
Can I quit or disable chronod?
There is no supported way, and nothing to gain. Its launch file starts it only when something asks for it, brings it back only if it crashes, and throttles restarts to one every 3 seconds, so quitting it in Activity Monitor buys you seconds of quiet before the next widget, timer or live activity calls it back. It also sets EnablePressuredExit, so the system reclaims its memory when it is idle, which is the polite version of quitting that macOS already does for you. The levers you actually have are the features: fewer widgets on the desktop and in Notification Centre, Use iPhone widgets off in System Settings under Desktop and Dock, and no booted simulators if you are a developer. Take the work away and the clerk goes quiet.
What is ChronoCore and com.apple.chronod?
ChronoCore is the private framework the daemon is built from, and its version file gives the project its real name: ProjectName Chrono, build 483. It is one of a whole family of frameworks with the same prefix sitting side by side on every Mac: ChronoKit, ChronoServices, ChronoUIServices, DistributedTimers, DistributedTimersDaemon, IdleTimerServices, MobileTimer, MobileTimerSupport, SiriTimeTimerInternal and TimerAppIntents. That list is the best one line description of the job: this is Apple's time and scheduling stack, the machinery under widget timelines, timers and live activities. com.apple.chronod is simply the launchd label, the name under which the rest of the system books appointments with it.
Ready? Buy Ribbon for $15, or read all the guides.