Tips and tricks

use the launchctl commands

launchctl load ~/Library/LaunchAgents/com.user.morning-alarm.plist
launchctl list | grep morning

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>

    <key>Label</key>
    <string>com.user.morning-alarm</string>

    <key>ProgramArguments</key>
    <array>
        <string>/Users/$USER/scripts/morning-alarm.sh</string>
    </array>

    <key>StartCalendarInterval</key>
    <array>
        <dict>
            <key>Weekday</key>
            <integer>2</integer>
            <key>Hour</key>
            <integer>10</integer>
            <key>Minute</key>
            <integer>0</integer>
        </dict>
        <dict>
            <key>Weekday</key>
            <integer>3</integer>
            <key>Hour</key>
            <integer>10</integer>
            <key>Minute</key>
            <integer>0</integer>
        </dict>
        <dict>
            <key>Weekday</key>
            <integer>4</integer>
            <key>Hour</key>
            <integer>10</integer>
            <key>Minute</key>
            <integer>0</integer>
        </dict>
        <dict>
            <key>Weekday</key>
            <integer>5</integer>
            <key>Hour</key>
            <integer>10</integer>
            <key>Minute</key>
            <integer>0</integer>
        </dict>
        <dict>
            <key>Weekday</key>
            <integer>6</integer>
            <key>Hour</key>
            <integer>10</integer>
            <key>Minute</key>
            <integer>0</integer>
        </dict>
    </array>

</dict>
</plist>

Introduction

Mac OS X provides a rich set of mechanisms for running code in the background—tasks that execute independently of a user’s active session. Whether you are building a daemon that starts at boot, a login item that launches when a user signs in, or a cron-like scheduled job, Apple’s frameworks give you powerful, system-integrated options for every use case.

This guide walks through the primary methods available to macOS developers: launchd (the recommended modern approach), Login Items, XPC Services, and the legacy cron scheduler. Along the way you will find complete examples, best-practice recommendations, and troubleshooting tips drawn from real-world development.

Why Background Tasks Matter

Modern macOS applications and system utilities frequently need to perform work outside the main application lifecycle. Common scenarios include:

• Syncing data to a remote server on a recurring schedule
• Monitoring file-system changes and reacting in real time
• Running maintenance routines during idle periods
• Providing system-wide services to other applications via IPC
• Launching a helper at boot without requiring the user to log in

Understanding which mechanism to choose—and how to configure it correctly—is essential to writing well-behaved, energy-efficient software that plays nicely with macOS security and privacy controls.

Method 1: launchd – The Modern Standard

Introduced in Mac OS X 10.4 Tiger, launchd is PID 1 on every macOS system—the first process the kernel starts and the parent of all other processes. It replaced the older init, mach_init, and SystemStarter mechanisms and is now the only Apple-sanctioned way to launch daemons and agents.

Daemons vs. Agents

launchd distinguishes two kinds of background jobs:

• Launch Daemons run as root (or another privileged user) in the system context. They start when the machine boots, before any user logs in, and they continue running whether or not a user session is active. Property list files live in /Library/LaunchDaemons/ or /System/Library/LaunchDaemons/.
• Launch Agents run in the context of a logged-in user. They can interact with the user’s GUI session and have access to per-user resources. Property list files live in ~/Library/LaunchAgents/ (per-user) or /Library/LaunchAgents/ (all users).

Creating a Property List (plist)

Each launchd job is described by an XML property list. The following example schedules a shell script to run every hour:

Save this file as ~/Library/LaunchAgents/com.example.myhourlyworker.plist (for a per-user agent).

Loading and Managing Jobs with launchctl

Use the launchctl command-line tool to load, unload, and inspect jobs:

Key plist Properties Reference

The most commonly used configuration keys:

Method 2: Login Items

Login Items are applications, bundles, or scripts that launch automatically when a user logs in to their account. They appear in System Settings → General → Login Items & Extensions, giving users full visibility and easy control.

SMAppService (macOS 13+)

Apple’s modern API for login items is SMAppService, introduced in macOS Ventura. It requires a helper executable embedded in your app bundle.

Legacy: LSSharedFileList (macOS 12 and Earlier)

For older targets you can use LSSharedFileList, though this API is deprecated. Prefer SMAppService for all new development and aim to ship a macOS 13 minimum deployment target where feasible.

Method 3: XPC Services

XPC (Cross-Process Communication) lets you split privileged or crash-prone work into a separate process that launchd manages on your behalf. The main app communicates with the helper over a type-safe, sandboxed connection.

When to Use XPC

• Privilege separation – run only the code that needs elevated rights in the helper
• Crash isolation – a helper crash does not bring down the main application
• Resource limits – apply tighter sandbox rules to untrusted data parsing
• Lazy launching – launchd starts the helper only when a connection arrives

Setting Up an XPC Service in Xcode

1. In your Xcode project, choose File → New → Target and select XPC Service.
2. Xcode creates the helper bundle inside your app’s Contents/XPCServices/ directory.
3. Define a shared protocol in a framework both targets link against.
4. Implement the protocol in the XPC service target.
5. Connect from the main app using NSXPCConnection.

Connecting to the service:

Method 4: cron – Legacy Scheduler

The classic Unix cron daemon is still present on macOS but is officially deprecated in favor of launchd. It is useful for quick personal scripts or compatibility with Unix tooling, but it does not integrate with macOS sleep/wake, power assertions, or Gatekeeper.

Edit your crontab with:

Best Practices & Common Pitfalls

Energy and Performance

• Use StartCalendarInterval instead of polling loops to let the CPU sleep between runs.
• Set ThrottleInterval on launchd jobs that may exit and relaunch rapidly.
• Call NSProcessInfo.processInfo.beginActivity(options:reason:) when your task must not be interrupted by App Nap or system sleep.
• Avoid wake locks longer than necessary; always balance beginActivity with endActivity.

Security & Sandbox Considerations

• Daemons in /Library/LaunchDaemons must be owned by root:wheel with permissions 644.
• Code-sign all executables and property list files for Gatekeeper compliance.
• Use App Sandbox entitlements sparingly in XPC helpers; grant only the minimum required.
• Avoid storing secrets in plist files or environment variables; use the Keychain instead.

Logging & Debugging

• Route output to /var/log/ (daemons) or ~/Library/Logs/ (agents) via StandardOutPath / StandardErrorPath.
• Use os_log / Logger for structured, privacy-aware logging visible in Console.app.
• Run log stream –predicate ‘subsystem == “com.example.myapp”‘ for live output.
• launchctl list shows PID (if running) and last exit status for quick diagnostics.

Choosing the Right Approach

Conclusion

macOS provides a mature, well-documented ecosystem for background processing. For the vast majority of use cases, launchd is the correct tool: it is energy-efficient, integrates with the system’s power management, respects the security model, and gives users visibility into what is running on their machine.

When your application needs to run privileged code or isolate crash-prone subsystems, reach for XPC Services. When you want an item to appear naturally in Login Items for the user to manage, use SMAppService. Reserve cron only for quick personal scripts where launchd would be overkill.

By choosing the right mechanism and following the best practices in this guide, your background tasks will run reliably, transparently, and with minimal impact on battery life and system resources.