Mac login items checklist for menu bar utilities

The useful rule is simple: let a Mac utility open at login when missing its early state would make the day worse. A microphone mute app, screen-time counter, system monitor, clipboard history, sync agent, backup helper, or file shelf can earn that. A converter, color tool, screenshot editor, or one-off maintenance app usually can stay manual.

Disclosure: I build TeenyApps, including TeenyScreeny and TeenyMute. My bias is toward small native menu bar apps. The checklist below is still strict: launch at login is not a prize. It is a responsibility.

Quick decision table

Start with Apple's login item list

Apple keeps the user-facing control in System Settings, General, Login Items & Extensions. The Open at Login list controls apps, documents, folders, volumes, and connections that open when you log in. The same settings area also exposes background activity for apps that perform tasks while the main app is not open.

That split matters. A visible login item and a background helper are different trust decisions. A menu bar icon you can click is easy to reason about. A hidden background item needs a clearer reason: sync, updates, device control, backup, or a helper that belongs to an app you actively use.

If startup gets weird, Apple's troubleshooting path is blunt and effective: make a list of login items, remove them, restart, then add them back one at a time. That is slower than guessing. It also finds the actual offender.

Keep state utilities alive from the first minute

A state utility is useful because it has context before you think to open it. That is why some menu bar apps should start automatically.

TeenyScreeny is a clean example. Its source registers launch-at-login through Apple's Service Management API, counts active Mac time once it is running, saves daily totals locally, handles sleep and wake, and starts a fresh day when the date changes. If the app starts late, the early part of the session is not part of the active-time record. That is a real cost if you use the counter to shape the day.

TeenyMute is the microphone version. Its settings include Launch at Login and a Microphone on Launch choice: unmuted, muted, or use last state. Its source applies that state on launch, but push-to-talk mode intentionally starts muted. If your first interaction after login can be a call, a voice note, or a screen recording, startup mic state is not cosmetic. It is the baseline.

Keep one-off utilities manual

Not every TeenyApps-style utility needs to be present all day. A local converter, URL encoder, color picker, PDF helper, or screenshot cleanup tool may be fast enough from Spotlight, Raycast, the Dock, or the Applications folder. Starting it every morning can add a menu bar icon you only use once a week.

The test I use is: would I notice a missing minute of data or the wrong first state? If yes, open at login. If no, keep it manual. That means a screen-time counter and mic mute app can earn startup. A batch image resizer probably cannot.

This is also the cleaner privacy habit. A utility that runs only when you ask has less time to hold data, watch state, or clutter the menu bar. Always-on tools can still be private and local, but they should explain why always-on is part of the product.

Use one restart test before trusting the setup

After you choose login items, restart once on purpose. Do not wait for a messy morning to learn what actually opens.

1. Open System Settings, General, Login Items & Extensions.
2. Remove anything that has no daily reason to open automatically.
3. Restart the Mac.
4. Before opening work apps, check the menu bar and Background Items list.
5. Confirm each remaining utility has its expected startup state.
6. Disable one item at a time if startup feels slower or a helper misbehaves.

For the TeenyApps pair in this cluster, the two checks are concrete. Does the screen-time counter start before work begins? Does the microphone state match the launch setting you intended?

Startup speed is not the only concern

People usually clean login items because startup feels slow. That is a valid reason, but it is not the only one. The better cleanup target is ambiguity.

If five apps start and you cannot explain why each one is there, the Mac is harder to trust. If a hidden helper appears in Background Items and you do not recognize the parent app, investigate it. If a utility starts but its menu bar icon is hidden by a menu bar manager, make sure you still have a way to see its state when the state matters.

The menu bar should not be a drawer of forgotten installers. It should be a small set of live controls you want available before the first app switch.

Common questions

Which Mac apps should open at login?

Open apps at login when they provide state you need before the first click: microphone mute, screen-time tracking, system monitoring, clipboard history, sync, backup, VPN, or a file handoff shelf. Keep occasional tools manual.

Should every menu bar app launch at login?

No. A menu bar app should launch at login only when its value depends on being present all day or on capturing state from the start of the session.

How do I troubleshoot Mac login items?

Use System Settings, General, Login Items & Extensions. Remove or disable suspect items, restart, then add them back one at a time until the startup problem returns.

Sources checked

• TeenyScreeny facts were checked against the TeenyScreeny homepage and local Swift source for launch-at-login settings, active-time tracking, saved daily records, sleep/wake handling, and local history.
• TeenyMute facts were checked against the TeenyMute homepage and local Swift source for launch-at-login settings, startup microphone state, last-state storage, push-to-talk startup behavior, and Core Audio mute handling.
• Apple Support: Change Login Items & Extensions settings on Mac.
• Apple Support: Remove login items to resolve startup problems on your Mac.
• Apple Developer Documentation: SMAppService.
• Apple Support: Control access to the microphone on Mac.