macOS Background Task Management (BTM) Explained
What Background Task Management is, which login items, agents and daemons it tracks since macOS 13 Ventura, what a record holds and what it cannot prove.
On this page
TL;DR. Background Task Management (BTM) is the macOS 13+ service that keeps a list of the login items, launch agents and launch daemons the system has seen, attributes each one to a developer, and tells the user when new ones appear. The daemon backgroundtaskmanagementd keeps that list in a single store, /private/var/db/com.apple.backgroundtaskmanagement/BackgroundItems-v<N>.btm, filed per user. For each item it records a name, the developer name and team identifier from the code signature, a type, a disposition (enabled, allowed, hidden, notified), and the paths of the plist and executable. On a live Mac, sudo sfltool dumpbtm prints the store. BTM Parser reads the file, or that text, in your browser.
This article is the entry point to the series. Each section links to a deeper one.
What BTM is
Apple added Background Task Management in macOS 13 Ventura. Apple's deployment guide describes it as the framework that makes login items, launch agents and launch daemons transparent to users, and says it works with all apps, regardless of how they were installed.
Before Ventura, a program could install a launch agent and nothing in the user interface would show it. Since Ventura, System Settings > General > Login Items lists those items with a switch for each, and the user gets a notification when new ones are added. Later releases renamed the pane Login Items & Extensions.
Several parts work together:
| Part | Role |
|---|---|
backgroundtaskmanagementd | System daemon in the private BackgroundTaskManagement framework, launchd label com.apple.backgroundtaskmanagementd. Registers items, keeps the store, answers System Settings, sfltool and MDM |
BackgroundTaskManagementAgent | Per-user agent that shows the notifications |
BackgroundItems-v<N>.btm | The store: one file for all users, a binary plist written with NSKeyedArchiver |
| Login Items in System Settings | The user interface over the store |
| sfltool | dumpbtm prints the store, resetbtm resets it |
| Endpoint Security | ES_EVENT_TYPE_NOTIFY_BTM_LAUNCH_ITEM_ADD and ES_EVENT_TYPE_NOTIFY_BTM_LAUNCH_ITEM_REMOVE events, available to security tools since macOS 13 |
| MDM | The managed login items payload approves items in advance, by team ID, bundle ID or launchd label |
What BTM tracks
BTM records background items of these kinds:
- Login items: apps opened at login, including an app that registers itself through SMAppService, and helper apps in an app's
Contents/Library/LoginItemsfolder. - Launch agents: per-user jobs, from
~/Library/LaunchAgents,/Library/LaunchAgents, or inside an app bundle. - Launch daemons: system jobs, from
/Library/LaunchDaemonsor inside an app bundle. - Apps and developers: grouping records. An app record lists the identifiers of the helpers it contains. A developer record groups items from the same team.
A plist placed directly in a LaunchAgents or LaunchDaemons folder is a legacy item. Apple's Endpoint Security header defines the legacy field of a BTM item as true when the item is a legacy plist. An item an app registers through SMAppService, with its plist kept inside the app bundle, is not legacy. The store keeps that difference as a bit of the item's type, and sfltool dumpbtm prints it as legacy agent or legacy daemon. More on the modern path in SMAppService and login items in macOS 13+.
What a record holds
| Field | What it tells you |
|---|---|
| UUID | Identifier of the record |
| Name | Display name: an app name, a label or an executable name |
| Developer Name | Organization name from the signing certificate, when BTM could attribute the item |
| Team Identifier | The 10-character team ID from the code signature |
| Type | What the item is, as a bit field: app, login item, agent, daemon, developer, plus modifiers such as legacy |
| Disposition | Its state, as a bit field: enabled, allowed, hidden, notified |
| Identifier | BTM's key for the item |
| URL | The plist, app or helper the item stands for |
| Executable Path | The program a launchd item runs |
| Parent Identifier, Embedded Item Identifiers | Links from an item to its app or developer record, and back |
| Generation | A counter; Apple does not document its meaning |
The records are kept per user, under the user's generated UID. sfltool dumpbtm prints one section per user, titled with the numeric UID and that UUID. Each field and bit is explained in reading sfltool dumpbtm output, and the store file itself in where the BTM store lives.
How an item gets in, and what the user sees
There are two routes. An app can register a helper with SMAppService; the record is created at registration. Or a plist appears in a launchd folder, written by an installer, a script or an intruder; BTM records it when the system meets the job. Apple does not document the exact trigger for legacy plists.
When a new item is recorded, the user is notified. On Ventura the notification was titled "Background Items Added". The wording has changed between releases, and managed items get their own wording. The notification is advisory. A legacy plist is not held back until the user answers: in practice the job loads and runs, and the user can switch it off afterwards. Apple documents that SMAppService daemons are different: they do not start until an administrator approves them.
The notified bit of the disposition records that the notification was posted. It does not show that anyone read it.
What BTM does not do
- It does not record launches. A record shows that an item was known and in which state. It does not show that the program ran, or how often.
- It does not keep a documented registration time. The time a record was created has to come from elsewhere: the unified log of
backgroundtaskmanagementd(subsystemcom.apple.backgroundtaskmanagement), file times, FSEvents. - It is not a history. Records leave when an app unregisters an item or the user removes it. Apple documents
sfltool resetbtmas resetting login and background item data. - It is not a guarantee that the user was told. Patrick Wardle showed ways to suppress the notification at DEF CON 31 (August 2023), some of them without root. A missing notification proves nothing.
Why investigators care
BTM is one place that lists persistence across every user, with attribution. Three properties make it useful:
- Attribution. Each item carries the developer and team BTM derived from the code signature. A launch agent that claims to be an updater but has no developer, or a team that does not match the vendor in its name, stands out.
- Independence from the plist. The record is kept by a system daemon in a protected folder, not next to the plist. An intruder who deletes the plist may leave the record behind, and an item whose plist is missing is a lead.
- Coverage. Items in app bundles, which a scan of the LaunchAgents folders never sees, are in the store too.
In the FIN-MBP-03 sample, the Mac of dana.whitlock, the store lists Microsoft, Google and Zoom helpers with their teams, and one more: a legacy agent com.example.updater with no developer name and no team identifier, whose executable sits in a hidden folder, ~/Library/Application Support/.updater. The record does not say when it arrived. The unified log of the same Mac shows backgroundtaskmanagementd registering it on 2026-09-14 at 10:13:02.512 UTC, and the store file was last modified at that time. The investigation is walked through in investigating Mac persistence with BTM.
Where to start
- Read the store: copy it, or run
sudo sfltool dumpbtm > btm.txt, as described in collecting the BTM store. - Load the file or the text on BTM Parser, or click Try a sample to see FIN-MBP-03.
- Compare BTM with launchd's own state: BTM vs launchd overrides.
FAQ
Which macOS versions have Background Task Management?
macOS 13 Ventura and later. From macOS 10.13 to 12, login items were kept in a per-user backgrounditems.btm file, and launch agents and daemons were not tracked in one place.
Does BTM block a new launch agent?
Not a plist installed directly in a LaunchAgents or LaunchDaemons folder: BTM records it and notifies the user, who can switch it off. Apple documents one case that waits: a daemon registered through SMAppService does not start until an administrator approves it.
Does the BTM store record when an item was added?
Not in a documented field. Use the unified log of backgroundtaskmanagementd (subsystem com.apple.backgroundtaskmanagement), the file system times of the plist and the executable, and the modification time of the store file.
Is an item with no developer always malicious?
No. Ad-hoc signed and unsigned programs, such as many open-source tools run as services from a home folder, have no team identifier either. It is a reason to look at the item, not a verdict.
Related articles
Frequently asked questions
Which macOS versions have Background Task Management?
macOS 13 Ventura and later. From macOS 10.13 to 12, login items were kept in a per-user backgrounditems.btm file, and launch agents and daemons were not tracked in one place.
Does BTM block a new launch agent?
Not a plist installed directly in a LaunchAgents or LaunchDaemons folder: BTM records it and notifies the user, who can switch it off. Apple documents one case that waits: a daemon registered through SMAppService does not start until an administrator approves it.
Does the BTM store record when an item was added?
Not in a documented field. Use the unified log of backgroundtaskmanagementd (subsystem com.apple.backgroundtaskmanagement), the file system times of the plist and the executable, and the modification time of the store file.
Is an item with no developer always malicious?
No. Ad-hoc signed and unsigned programs, such as many open-source tools run as services from a home folder, have no team identifier either. It is a reason to look at the item, not a verdict.