Home / Install on macOS
Install Pling Agent on your Mac
Pling Agent lets you see and control your Mac from your iPhone, and sends the Mac’s stats and alerts to Pling. A menu-bar app for macOS Sequoia (15) and later, on Apple silicon and Intel.
Set up in four steps
Open the disk image, drag Pling Agent to Applications and open it. Its setup assistant takes it from there:
- Sign in to Pling with Apple or Google.
- Let your iPhone see and control this Mac. Turn on Pling Agent under Screen & System Audio Recording and Device Control and Data Access (called Accessibility before macOS 27) in Privacy & Security. The assistant opens each one and ticks it off as you go.
- Turn on Remote Login. One click in the assistant; macOS asks for an administrator’s password once.
- Open Pling on your iPhone. Signed in to the same account, your Mac is already listed under Screen › Your Macs. Not signed in there? Scan the code the assistant shows. The first time, Pling asks for the password you use to log in to the Mac.
Adding another iPhone? Click the Pling Agent icon in the menu bar and choose Connect iPhone… to show the code again.
Install the app with Homebrew instead
brew install --cask jeramo/pling/pling-agent
Headless Mac or server: install from the command line
The command-line agent sends stats and alerts and runs scheduled commands, with no menu-bar app.
Homebrew (command line)
For a headless Mac or a server, install the command-line agent, then set your API token. set-token writes the config and starts the brew service.
brew install jeramo/pling/pling
pling set-token <YOUR_TOKEN>
Verify it's running:
pling status
brew services list | grep pling
set-token. Only the command-line installs need it; the menu-bar app signs in instead.Curl one-liner
Skip Homebrew entirely. The installer downloads the latest signed and notarized binary, prompts for your token, and registers a per-user LaunchAgent.
curl -sSL https://raw.githubusercontent.com/Jeramo/pling-agent/main/install.sh | sh
The LaunchAgent autostarts on login. Logs go to ~/Library/Logs/pling-agent.log.
Manual install
Pick this when you want full control or to install on a Mac without admin privileges. Replace arm64 with amd64 on Intel Macs.
curl -L -o pling \
https://github.com/Jeramo/pling-agent/releases/latest/download/pling-darwin-arm64
chmod +x pling
sudo mv pling /usr/local/bin/
pling set-token <YOUR_TOKEN>
Configure
Print the active config path:
pling config
Edit it in $EDITOR:
pling config edit
Typical fields: api_url, token, metrics_interval.
Update
Homebrew:
brew upgrade pling
brew services restart pling
Curl install: re-run the install script. It replaces the binary and restarts the LaunchAgent.
Uninstall
pling uninstall
Removes the binary, config, and service registration. Homebrew installs can also be removed with brew uninstall pling.
Frequently asked
Why does Pling need Remote Login on macOS?
Your iPhone connects to the Mac through Remote Login, the secure sign-in built into macOS. Stats, alerts and scheduled commands work without it; seeing and controlling the screen doesn’t. In Remote Login’s ⓘ options, Allow access for must include your account: choose All users, or click + and add yourself.
Does Pling Agent work on Apple silicon?
Yes. Native arm64 binaries are shipped alongside Intel x86_64 builds. The installer and the Homebrew tap pick the right architecture automatically.
Are macOS binaries notarized?
Yes. Every release is signed with Developer ID and notarized by Apple, so Gatekeeper does not block the binary.
Where is the macOS config file?
When installed via Homebrew the config lives at $(brew --prefix)/etc/pling/config.toml. The curl installer writes /etc/pling/config.toml. Run pling config to print the active path on this machine.
How do I view agent logs?
Run pling logs -f to tail logs. Homebrew installs route through brew services; LaunchAgent installs write to ~/Library/Logs/pling-agent.log.
How do I update Pling Agent?
Homebrew: brew upgrade pling && brew services restart pling. Curl install: re-run the install script; it replaces the binary and restarts the LaunchAgent.