Install on macOS
Install AgentGarm on macOS from the signed package, then start its services.
Install the package
Download agentgarm-X.Y.Z-universal-apple-darwin.pkg from the download page, verify it, and open it, or install it from a terminal:
sudo installer -pkg agentgarm-X.Y.Z-universal-apple-darwin.pkg -target /It runs on macOS 15 and later, on Apple silicon and Intel.
Start the services
The package installs the programs and runs no script. An administrator then installs the daemon, the per-user session service and each agent's managed hooks, which nothing installs by itself: without them no command or file rule is decided. agentgarm doctor checks the result:
sudo agentgarmd install
sudo agentgarmd install --session
sudo agentgarmd hooks install claude-code # once per agent: codex, cursor, …
agentgarm doctorThe session service is installed for every user and starts at each user's next login. To start it now, run this as yourself before agentgarm doctor:
launchctl bootstrap gui/$(id -u) /Library/LaunchAgents/com.agentgarm.session.plistEach agent's guide covers its hooks: Claude Code, Codex, other agents.
Then follow the quick start, and once it runs:
Add the computer-use airbag (optional)
Only for an agent or MCP server that must drive the desktop preview: the airbag, AgentGarm Airbag, a background app beside agentgarmd, runs in each login session under its own LaunchAgent and drops such an agent's input on protected targets. Install it, then allowAgentGarm Airbag in System Settings, Privacy & Security, Accessibility when macOS asks; agentgarm doctor checks it. On an upgrade, running the install again restarts it on the new binary. sudo agentgarmd uninstall removes it with the service, and sudo agentgarmd uninstall --airbag removes it alone (govern computer-use agents).
sudo agentgarmd install --airbag
agentgarm doctorUpgrade
Verify the new release's package, install it over the old one, then restart the services: no package runs a script, so the old daemon keeps running until you do, and agentgarm status and agentgarm doctor say it needs a restart. When a release's notes say its service unit changed, run sudo agentgarmd install before the restart. Your policies, the audit log and the store carry over as they are; the restarted daemon points the agents' hooks at the new release by itself, and agentgarmd hooks status says stale for one it has not reached yet.
sudo installer -pkg agentgarm-X.Y.Z-universal-apple-darwin.pkg -target /
sudo launchctl kickstart -k system/com.agentgarm.agentgarmd
launchctl kickstart -k gui/$(id -u)/com.agentgarm.session # as each user
sudo agentgarmd install --airbag # only if you added the airbag: restarts it
agentgarm doctorRemove it
Uninstall the daemon first: it removes every agent hook and MCP configuration it installed, restoring what was there before, then its service. If one cannot be removed, the service is kept and the command fails and lists it, because a fail-closed hook left behind would deny every call of its agent; fix what it lists and run it again (--force removes the service anyway, and still fails). Then the session service, then the package. A session already running keeps running until its user logs out.
sudo agentgarmd uninstall
sudo agentgarmd uninstall --session
sudo rm -rf /Applications/AgentGarm.app /usr/local/share/agentgarm /usr/local/share/doc/agentgarm
pkgutil --only-files --files com.agentgarm.cli | grep '^usr/local/bin/' | sed 's|^|/|' | sudo xargs rm -f
sudo pkgutil --forget com.agentgarm.cliYour policies, the audit log and the store stay in /Library/Application Support/AgentGarm, so a later install picks them up. Export the audit log first if you need it (the audit log guide), then delete that directory to remove them too. A presence key is not removed: on a Mac its handle stays in each user's ~/Library/Application Support/AgentGarm/presence (the key itself never leaves the Secure Enclave), and on Linux a security key keeps its credential.