Why apps keep adding themselves to your login items

Apps add themselves to your login items because their makers want them ready the moment you need them, and because many apps come with a helper that has to run in the background to sync, check for updates or watch for something. It is usually not malicious, but it is rarely asked for either. You can say no in System Settings under General > Login Items & Extensions (Login Items on macOS 14), and you can check the list after every install.

Here is what is actually being added, why, where you get a say, and a quick habit that keeps the list honest.

What “adding itself” really means

When an app wants to run at login, macOS gives it a few ways to ask. Some ask politely, with a setting inside the app such as “Open at login”, which you can leave off. Others register a background item without much ceremony, and macOS shows a “Background Items Added” notification.

It helps to know there are three different things that all look like “the app is in my login items”:

1. The app itself, set to open at login. You will see its window or its menu bar icon appear when you sign in.
2. A helper that belongs to the app. It has no window. It runs in the background so that the app can sync files, update itself, or respond to a shortcut.
3. A launch agent or daemon, which is a file that tells macOS to start a program at login or at boot. Apps that install a helper this way are asking for the same thing as the other two, only through an older door.

Most of the surprise people feel comes from the second and third kind. You installed one app and now there are two or three entries with names you do not recognise. Launch agents and daemons explained in plain English covers what those files are.

Why they do it

There are honest reasons and less honest ones, and both are common.

Speed. An app that is already running opens at once when you click it. For apps people use all day, such as chat, notes or a clipboard tool, that is a real benefit.

Syncing and updates. A cloud storage app has to run to keep your files in sync. Many apps ship a separate updater that checks for new versions and installs them. Where Mac apps hide their updaters goes into that one.

Features that need to listen. Anything that responds to a keyboard shortcut, a copied item or a connected device has to be running before you press the key.

Habit and metrics. Some apps add themselves because it keeps them in front of you, or because the default was chosen for the maker’s benefit, not yours. Some apps switch “open at login” on by default, and many people never change a default.

You do not have to work out which reason applies. Ask a simpler question: would I be unhappy if this did not start by itself?

Where you can say no

You have three places to look, from the one you should use first to the one that needs more care.

In the app. Many apps have a setting for it, often in Settings or Preferences, worded something like “Open at login” or “Launch at startup”. Turning it off there is the cleanest way, because the app removes its own entry.

In System Settings. Open Login Items & Extensions in System Settings. “Open at Login” lists the apps that start with you, and you can remove an entry with the minus button. Below it, “Allow in the Background” lists helpers that apps have registered, each with a switch. Turn off the ones you do not want. This is the screen the “Background Items Added” notification points you to.

In the startup files themselves. Launch agents and daemons are files in a few Library folders. They do appear under “Allow in the Background”, but often under the maker’s company name rather than the app’s, and a switch turns one off without removing the file. How to find out what starts when your Mac starts shows where the files are, and it is the place to go if you cannot match an entry to an app.

A word on the switches: turning off a helper can stop a feature you do want. If a cloud app stops syncing or a utility stops responding to its shortcut, switch the helper back on. Nothing is lost, because you only changed whether it runs.

Why the same app comes back

Sometimes you remove an app from “Open at Login” and it returns after the next update. An app can add itself again when it opens, and an installer can set the entry again. If it keeps coming back, the app’s own setting is the one to change, because removing the entry in System Settings does not stop the app asking again.

If an app opens again after you quit it, that is a different problem, with a different cause. See why an app keeps reopening after you quit it.

A habit that keeps the list honest

The easiest time to deal with this is right after you install something. It takes under a minute.

1. Install the app and open it once.
2. Open Login Items & Extensions in System Settings.
3. Compare the list with what you saw last time. Anything new that you did not ask for can go.
4. Check the app’s own Settings for an “Open at login” option and decide there.

If you pay attention to the notification macOS shows when an item is added, you will also catch many of these at the moment they happen. It is titled “Background Items Added”, it usually names the app or its maker, and it is easy to dismiss without reading. Read it once, and you will know which app caused it.

A second view of the same list

Foreman has a Startup Apps page that gathers everything that opens at login or runs in the background in one place: login items, launch agents and daemons, and the background items apps register. They are grouped by the app they belong to and shown with readable names, so three entries from one installer appear as one app with its parts. Each item has a status, and you can Disable or Enable it. With Full Disk Access, Foreman can also read the “Allow in the Background” switches; without it, it shows a note you can skip. Items an app registered through macOS’s own login items system can only be changed in System Settings, so Foreman opens it there for you.

That is the extra Foreman offers over the System Settings screen: one list grouped by app, with readable names and “Impact now”, which shows whether each item is running and how much it uses. It is $12 once, free for 24 hours, and the checking habit above works without it.

Quick answers

Is it safe to remove them? Removing an item from login only stops it starting automatically. The app is not deleted. If you are unsure of an item, leave it until you know what it does.

Will the app still work? Yes, you open it by hand. Only features that depend on the background helper, such as sync or a global shortcut, will wait until the app is running.

How often should I check? After you install anything new, and once in a while after that.