Background Items Added: the notification that names what just registered itself
A notification says background items were added to your Mac. What it means, where the list actually lives, and how to check or remove what was added.
By Chethan Kumar S N · Updated
A notification appears in the corner of the screen, it mentions background items, and it is gone before you finish reading it. Searching for it produces a wall of advice that ranges from “this is normal” to “you have malware”, and almost none of it tells you where the list is or who put the item on it.
The notification is real and the mechanism is not mysterious, but there is one fact that makes all of it click: the message is being posted by a process on your own Mac, out of a file it can name, about an entry that has just been written to a database you can point at. Everything below comes from reading those files on a 14 inch MacBook Pro with an M1 Pro running macOS 27.0.1, from Apple’s own documentation, and from thirteen hours of the system’s own log for the component that does the work. Nothing was uninstalled, no setting was changed, and nothing was quit.
What the notification is really telling you
It is telling you that an item was added to a list. That is the whole event.
macOS keeps a register of everything that is allowed to run in the background: apps you turned on, helpers that apps installed for themselves, launch agents that came with an installer, Spotlight importers, and dock tiles. When an entry is added to that register, the system records it and posts a notification so the addition does not happen silently. Before macOS 13 that register was assembled from property list files dropped into a handful of directories, and nobody saw a notification because nobody was watching. Apple’s own deployment guide describes the change plainly: before macOS 13, helper executables came with installer scripts that wrote property lists into specific directories, and from macOS 13 onward there is a new structure that works out of the app bundle itself.
So the honest answer to “what did I just install” is usually nothing. An app you already had registered a helper, or an updater replaced one. The register is the interesting object, not the notification.
The two processes behind it
There are two, and they do different jobs.
The first is a daemon that runs as root, was started at boot, and owns the list. On this Mac it has been up for 25 days without being restarted:
| Check | Result on this Mac |
|---|---|
| Path | /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Resources/backgroundtaskmanagementd |
| Runs as | root, parent process 1, so launchd started it |
| Memory | 11,200 KB, after 25 days and 5 hours of uptime |
| Architectures in the binary | x86_64, arm64e, arm64e.x1 |
| Signing | Identifier com.apple.backgroundtaskmanagementd, Platform identifier 26, signed 9 August 2026 |
| KeepAlive in its own job | none, and EnablePressuredExit is set to false |
| launchctl run count | runs = 1, last exit code = never exited |
That last row is worth a sentence. A daemon that has run exactly once, in 25 days, and has never exited, is the shape of something that is not going to be restarted on a whim. Its job file also exposes four Mach services, which are the names other processes use to talk to it: com.apple.backgroundtaskmanagement, .registrar, .responses and .sfl. SFL is the shared file list, the older mechanism that used to hold login items, and its continued presence in the same daemon is the seam between the two generations.
The second process is the one that shows you the notification. It is a small app inside the same framework, at /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Support/BackgroundTaskManagementAgent.app, with LSUIElement set to true so it has no Dock icon and no window, and LSMinimumSystemVersion set to 27.0. Its binary is 527,536 bytes, less than half the size of the daemon. It is not always running: RunAtLoad is false, and its job is started by events, specifically by com.apple.LaunchServices.applicationRegistered on the distributed notification stream, which is macOS saying “an application just registered itself”. When that fires, the agent runs, decides whether a notification is owed, posts it, and goes away.
Its own record of itself says it has run twice, that its minimum runtime is 10 seconds, and that its last exit reason was JETSAM_REASON_MEMORY_PERPROCESSLIMIT, the system reclaiming it. Among the services it publishes is one with an unusually honest name: com.apple.usernotifications.delegate.com.apple.BTMNotificationAgent. That is the notification delegate, and it is why the thing you saw on screen exists.
The notification’s words are in the agent
This is the part most write ups miss. The agent’s binary carries the text of the notification as named strings, and reading them settles a lot of guessing:
Title: Login Item AddedTitle: Multiple Items AddedTitle: Multiple Extensions AddedTitle: Managed Login Items AddedTitle: App Running in BackgroundSuffix: You can manage this in Login Items & Extensions.Suffix: You can view these in Login Items & Extensions.Suffix: You can manage background activity in Login Items & Extensions.Suffix: You can manage background apps in the Dock and in System Settings.Apps run in the background to perform tasks such as updating or syncing data.Your organization added software that can run in the background.
Two things follow. The first is that there are several flavours of this notification, not one, which is why two people comparing screenshots can describe different words for the same event. The second is that the last two lines are the body text: one for an app doing it, and one for a management profile doing it on a managed Mac. If you are on a work machine and the notification mentions your organisation, an administrator’s configuration pushed the item, and the notification is Apple telling you so.
The agent also names the methods that build the message, and the names describe the behaviour exactly: getCoalescedTitle:body:forItem:container:types:backgroundCount:extensionsCount: and postCoalescedNotificationForItem:container:backgroundCount:extensionsCount:types:reply:. Coalesced is the key word. Several additions get merged into one notification with a count, rather than one notification each.
The screen it points you at is also a file you can read
Every notification ends by pointing at Login Items & Extensions, so it is worth knowing that the pane is not built into System Settings. It is a separate application extension at /System/Library/ExtensionKit/Extensions/LoginItems.appex, with the identifier com.apple.LoginItems-Settings.extension and version 1.1.
Its own string table, 26 English strings across 42 languages, is a faithful description of the screen:
| The pane’s own wording | What it labels |
|---|---|
| Open at Login | The list of things that open when you log in |
| Background App Activity | The section that answers this notification |
| These items will open automatically when you log in. | The subtitle under the first list |
| These apps can automatically run in the background to do things like sync data and check for updates. | The subtitle under the second list |
| Last ran in background today | Per item, when it last did something |
| Running in background / Not running in background | The per item state |
| Item from unidentified developer. | Shown when Apple cannot name the owner |
| Legacy Background Tasks | Older items that predate the current mechanism |
| Managed Background Apps | Items pushed by a management profile |
| You cannot remove items managed by profile. | The reason the Remove button is dead |
| These background items are managed by a profile. | With a link straight to Device Management |
| Allow command line tools to be used for automating scheduled background tasks. | The switch for scripting |
One small discrepancy is worth recording because it trips people up when they search. Apple’s web page calls the second list row App Background Activity, and the pane on this Mac says Background App Activity. Same feature, two word orders, and neither word order finds the other in a search box.
Where the list actually lives
The register is a file, and the path is printed in the system log every time it is written:
/var/db/com.apple.backgroundtaskmanagement/BackgroundItems-v18.btm
There is a second one per user, in the same folder, named BackgroundItems-v18-<UUID>.btm, so a shared Mac can hold several. On this Mac the folder is owned by root, and trying to list inside it returns Operation not permitted, which is macOS protecting it rather than a fault. The folder’s own modification time was 14 November at 18:12, and the log shows why it moves: the string saveStoreForUserIdentifier: user store saved to appears 1,932 times in thirteen hours. The file is not rewritten on a timer, it is rewritten whenever an item changes or is used.
The log also shows the identifiers the store uses, and they carry a numeric prefix that says what kind of thing each item is. Three of them appeared on this Mac: identifiers beginning 8. for the entries whose property lists sit in ~/Library/LaunchAgents, which the log labels type=legacy agent; 64. for the Outlook Spotlight importer, type=spotlight; and 2. for app bundled items, type=app. The full set of types the log mentions also includes type=daemon, type=dock tile and type=background tasks.
Watching one item go in is more instructive than reading about it. The line looks like this, trimmed:
registerLaunchItem: found existing item: uuid=C7664E20-367E-4C14-A32F-76104BF48A61,
name=zsh, type=legacy agent, disposition=[enabled, allowed, notified],
identifier=8.dev.copperriver.notes-sync, url=file:///Users/.../LaunchAgents/dev.copperriver.notes-sync.plist
Note the third field after the word disposition. notified is a flag, and it is this flag that decides whether you get told.
How often the list is consulted
Thirteen hours of the system’s log for the background task subsystem is 883,769 lines. Most of that is not changes, it is queries, and the shape of the traffic is the most useful thing in the whole exercise.
| Message | Lines in thirteen hours |
|---|---|
| getEffectiveDisposition: | 58,680 |
| effectiveItemDisposition: | 58,678 |
| effectiveItemDispositionWithAuditToken: | 58,633 |
| registerLaunchItem: | 172 |
| noteUseOfItem | 66 |
| checkTasksAllowedInBackgroundForAppURL: | 29 |
Fifty eight thousand disposition checks against 172 registrations. The list is read constantly and written almost never, which is the correct design for something that has to answer “may this run?” before every background launch.
And the queries came from only four processes in that window. Two of them accounted for everything: one process asked 43,864 times, and a helper for a locally built app asked 14,766 times. The rest asked twice and once. A single well behaved agent, checking whether it is still allowed, at roughly thirty times a minute, is the entire reason that log is nearly a million lines long.
The disposition itself is a small tuple, and the counts are informative:
| Disposition seen | Count |
|---|---|
[enabled, allowed, notified] | 44,016 |
[enabled, allowed, not notified] | 14,778 |
[disabled, allowed, notified] | 1 |
Three flags in order: is it enabled, is it allowed, and has the user been told. The third one is why you can install five things in a month and only remember two notifications. Whether the flag is set depends on whether you have already been told about that item, not on how important the item is.
There is one more line worth quoting, because it is the answer to a question people ask about their own apps: checkTasksAllowedInBackgroundForAppURL: result=record not found (-95). That is an app asking whether it may do background work and being told it is not in the register at all. Apple’s documentation treats this as the normal state before an app has been granted anything.
Where the friendly names come from
Some items in the list have a name you recognise and others sit under a generic heading. The difference is a single lookup table, shipped inside the same framework:
/System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/Resources/attributions.plist
Apple’s deployment guide describes it: a preference file that contains many applications’ helper apps and executables, kept so their helpers can be attributed to the right name. On this Mac it holds 252 entries, 218 of which carry a team identifier, and 103 distinct attribution names ranging from Microsoft AutoUpdate to AutoCAD to Jamf Self Service.
Cross checking it against the twenty seven launch items actually installed on this Mac is the honest test, and the result is that six resolve and twenty one do not. Microsoft AutoUpdate resolves by matching its label exactly, which is why that one always has a name. A Cisco helper whose entry exists in the file is matched by the label Apple listed years ago. And then there are the items nobody has ever heard of, which is where the framework’s own string table comes in: it contains the pair Unknown Developer mapped to Other Developers. That single line is why some rows in the pane look anonymous, and it is not a warning about them.
What Apple’s own documentation says
Four pages are worth reading before you act on any of this.
The settings page, Change Login Items & Extensions settings on Mac, describes the pane exactly as it is: an administrator can select the apps, documents and server connections that open at login, and turn Apple and third party extensions on and off. Its row for the second list reads App Background Activity: Allow apps to perform tasks when the app isn't open, such as checking for software updates or syncing data. It also explains the yellow warning triangle: an item with a triangle next to it will not open automatically because it was moved or deleted.
The second page, Open items automatically when you log in on Mac, is where the one genuinely useful shortcut lives. To stop login items opening just for one session, hold Shift while you click Log In at the login window, or hold Shift during the progress bar at startup. Nothing is removed, nothing is forgotten, the next normal restart brings them all back. For isolating a suspect, that is a two second test.
The third page, Remove login items to resolve startup problems on your Mac, gives the careful version: list the items, remove all of them, restart, then add them back one at a time and restart after each, removing only the last one you added when the problem returns. Everyone writes the first half of that advice. The second half is the part that identifies the culprit instead of blaming the group.
The fourth is the enterprise guide, Manage login items and background tasks on Mac, and it is the most informative of the four even for a single user machine. It names the diagnostic tools: sfltool dumpbtm prints the current status of login and background items, and sfltool resetbtm resets the data, with a recommendation to restart between tests. It gives the log command for watching the management side live, filtering on subsystem = 'com.apple.backgroundtaskmanagement' and category = 'mcx'. It explains what changed in macOS 13, that the new structure works through the SMAppService object inside an app’s own bundle, and it lists the profile rules an administrator can use to pre approve items by bundle identifier, bundle identifier prefix, team identifier, or the label of the launchd job. It also records a macOS 26 change that explains a newer kind of prompt: if background tasks started by an app are still active after a user quits the app, the user is now asked whether to allow them to remain active.
sfltool itself is unglamorous. Its usage line reads sfltool csinfo|dumpbtm|archive|clear|resetbtm|resetlist|list|list-info [options]. Running sfltool list on this Mac printed 21 shared file list names, including com.apple.LSSharedFileList.SessionLoginItems, GlobalLoginItems, SFLServiceManagementLoginItems and ManagedSessionLoginItems. Asking about the old session login list by name returned the name and nothing else, an empty list, which is the seam from earlier showing up in practice: the older list is empty on this Mac because its items live in the newer store.
What to do about the notification
Mostly, nothing. It is a report, not a request. If you want to act, the useful actions are these.
Look at the list once, in System Settings under General, then Login Items & Extensions. You are looking for two things: an item you did not expect, and an item whose state is Running in background when you thought it was closed. The pane’s own string Last ran in background today answers the second question directly, and it is the detail that makes the list worth opening.
Turn off what you do not need rather than removing it. Switching a background item off stops the work. Removing a login item stops it opening. Neither uninstalls the app, and neither is permanent in the way people hope, because the app will offer to add itself back the next time it updates.
If an item is marked as managed, leave it. The pane tells you it came from a profile and gives you a link to Device Management. The string is You cannot remove items managed by profile., which is a limit rather than an error.
An item can also outlive the app it belongs to. The app bundle and the login item are two separate things, and moving the app to the Bin does not remove the entry, which is why Apple recommends using a developer’s own uninstaller when there is one. If a name in the list belongs to something you thought you had deleted, the uninstall page shows how to look up the identifier behind it and find what the app left in your Library.
And if you want to clear the history rather than the items, note that sfltool resetbtm is the tool Apple names for it, and that it is a reset rather than a tidy up: Apple recommends restarting afterwards, and the list is rebuilt from what is actually installed.
What this page cannot tell you
Apple publishes no list of which background items are safe, because the answer depends entirely on which apps you installed. Any site offering a definitive list of “bad” background items is guessing about your machine.
The notification text is not fully documented either. The four titles quoted above come from reading the agent’s own binary on macOS 27.0.1, and string tables change between releases, so a different build can word the same notification differently.
And the notification carries no timestamp and no undo. It is a one time message with a count, so if you miss it, the list in System Settings is the only record. That is the reason this page spends more words on the list than on the popup.
Where window managers fit
Nothing here is a window problem, and no amount of background hygiene makes a desktop easier to work on. The two do meet at the same symptom, though: a Mac that feels busy. Background items are the invisible half of that feeling, and windows are the visible half, which is usually things shrunk into the Dock, a desktop with nineteen overlapping windows on it, and Control Up used as a search expedition.
Ribbon takes the other approach. Windows stay at full size on a single scrolling strip instead of stacking, so the window you want is one swipe away and nothing disappears behind anything else. 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. You can drive the strip in your browser before installing anything.
The short version
The notification means an entry was added to macOS’s register of things allowed to run in the background. It is posted by Apple’s own agent inside the BackgroundTaskManagement framework, and the register itself is a file at /var/db/com.apple.backgroundtaskmanagement/BackgroundItems-v18.btm.
Two processes are involved. A root daemon owns the list and had run exactly once in 25 days on this Mac. An on demand agent posts the notification and carries the wording of it, which is why the text mentions Login Items & Extensions and why several additions arrive as one coalesced message with a count.
The list is read far more often than it is written: 58,680 disposition checks against 172 registrations in thirteen hours, from only four processes. That is the whole event, and it is why the notification feels random. It is not on a schedule, it is on a write.
Names come from a 252 entry attributions file, which resolved six of the twenty seven items installed here. The rest are grouped under Other Developers, which is a label rather than a warning.
If you open System Settings and read the list once, you will know more about it than the notification will ever tell you. If you want to stop something opening without deleting anything, hold Shift at login for a single session, and if you want the diagnostic view, sfltool dumpbtm is the command Apple names, with the caveat that it is an administrator level tool.
Questions
What does the Background Items Added notification mean?
It means something registered itself to run in the background on your Mac. Nothing has been installed behind your back in the sense people fear: an app you already have, or an update to one, declared a background task, and macOS recorded it in a list and told you. On this Mac that list is kept by a system daemon in the file /var/db/com.apple.backgroundtaskmanagement/BackgroundItems-v18.btm, and the notification is the visible tip of that write. The two things worth knowing are that the notification does not block anything, and that it will keep appearing every time a background item is added, which is why people see it after an app update rather than once in the life of the machine.
Is Background Items Added a virus?
No, and the notification itself is the opposite of a virus: it is macOS making visible something that used to be invisible. The process that posts it is Apple's own /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Support/BackgroundTaskManagementAgent.app, a signed system app with no Dock icon, and the daemon that owns the list runs as root out of the same framework. What the notification tells you is that an item was added to the background list. Read the list rather than the notification, because the list names the owner: on this Mac, six of twenty seven registered items resolved to a real name such as Microsoft AutoUpdate or Jamf Self Service, and the rest fall under Other Developers because Apple's attribution file has never heard of them.
How do I see or remove the background items that were added?
Open System Settings, then General, then Login Items & Extensions, and scroll to the list under Open at Login and the section below it for background activity. The pane is a real app on disk at /System/Library/ExtensionKit/Extensions/LoginItems.appex, and its own strings say what you will see: Open at Login, Background App Activity, Running in background, Not running in background, and a line that reads Last ran in background today. Removing an item stops it opening or running at login, and it does not uninstall the app that owns it. Items installed by a management profile cannot be removed at all, and the pane says so with the string You cannot remove items managed by profile.
Why does it keep coming back even after I remove things?
Because it is reporting an event, not a state. Each background item that gets registered produces its own record, and an app that updates itself, or reinstalls its helper after an update, registers it again. The notification is coalesced, which is why several additions in a row arrive as one message rather than five: the agent on this Mac carries the string Multiple Items Added next to Login Item Added. If the same app appears in the list every few weeks, that is the app's update cycle, not something repairing itself.
Should I click Allow or Deny when a Mac asks about background tasks?
Allow if you want the app to do the thing it is asking about, which its own wording spells out in the alert: Apps run in the background to perform tasks such as updating or syncing data. Deny if you would rather it only worked while it was open in front of you, and nothing breaks, the app simply loses the ability to do work when it is not running. The buttons carry those exact words because they come from the framework's own string table, where BACKGROUND_ITEM_ALERT_ALLOW is Allow and BACKGROUND_ITEM_ALERT_DENY is Deny. macOS 26 added a second prompt for a related case: an app's background task that is still running after you quit the app now asks you whether it should stay active.
Ready? Buy Ribbon for $15, or read all the guides.