Getting started - macOS

Install the NP4th Mac agent, grant required permissions, sync org config, and confirm background probes via launchd.

Prerequisites

• An NP4th organization with an Owner or Admin account
• A macOS package from your admin (dashboard download when published)
• Outbound HTTPS to https://app.np4th.com
• Permission to install apps under /Applications

Install

1. Obtain the macOS package for your organization.
2. Install NP4th.app to /Applications.
3. Launch NP4th. If the package was not pre-baked, enter your tenant slug and agent key (from Settings → Agent keys).

Permissions

Grant when prompted:

• Local Network — required for many probe types on modern macOS
• Location — used when available for map placement (Hop 1)

If ping (ICMP) is restricted by the OS, TCP and TLS checks still run. See Troubleshooting.

Sync config and run a test

1. Click Update config to pull the latest targets, service packs, and Test interval from the server.
2. Choose Run full test or Run selected.
3. Confirm the run appears under Runs & map on the dashboard.

launchd background agent

Background probes use launchd with NP4th --agent (headless):

1. Copy packaging/com.didurlabs.np4th.plist into ~/Library/LaunchAgents/ (edit paths and StartInterval as needed).
2. Ensure client-config.json sits next to the binary with apiBaseUrl, tenantSlug, and clientKey.
3. Load: launchctl load ~/Library/LaunchAgents/com.didurlabs.np4th.plist

The agent syncs config on an interval, uploads scheduled runs, and honors dashboard Run now commands.

• Label: com.didurlabs.np4th
• Program: /Applications/NP4th.app/Contents/MacOS/NP4th --agent
• RunAtLoad is enabled; StartInterval defaults to 300 seconds (aligned with org interval when synced)

Device identity uses the Mac hardware UUID (IOPlatformUUID), so reinstalls on the same Mac keep the same agent record when the key remains valid.

Verify

1. On the dashboard, open Installed agents and confirm the Mac shows as online (heartbeat or run upload within about 15 minutes).
2. Open Runs & map, expand the computer, and inspect per-target results.
3. If the agent is missing, confirm launchd is loaded and the agent key is enabled.