Skip to the content

Deploy AgentGarm with MDM

Roll AgentGarm out to managed Macs, Linux machines and Windows PCs: the packages, the services, the macOS approvals and the browser extension.

Built, not yet claimed preview: this guide describes a package that has not passed its release gate.

Push AgentGarm to your fleet with the tools you already use: Jamf or another macOS MDM for the package, the system extension and privacy approvals, your configuration management on Linux, and Intune on Windows, plus browser policies that force-install AgentGarm's extension and let it reach the machine's agentgarmd. At the end each machine runs AgentGarm's services and is ready to enrol in Central Lite. Parts of this wait on store listings and release signing, so the guide is a preview.

1. Fill the templates with fill.sh

The release tarball carries AgentGarm's MDM templates, fill.sh and the macOS post-install script in share/agentgarm/mdm; the .deb, .rpm and .pkg do not. fill.sh reads the browser extension's store ids, the extension's action on a secret and AgentGarm's Apple Team ID from extension.env beside it, fills every template, and writes the results under --out. It installs nothing, and it refuses a malformed value or a placeholder left unfilled.

Today extension.env holds no ids, because the extension is not yet listed in the Chrome Web Store or Edge Add-ons, so fill.sh writes no browser files until a release fills them. It writes the browser files for each browser whose id is set, and the four macOS host profiles once the Team ID is set, in extension.env or with --apple-team-id.

share/agentgarm/mdm/fill.sh --out agentgarm-mdm

2. Force-install the browser extension

Each browser's file sets four policies for Chrome or Edge: ExtensionInstallForcelist, with the extension's store id and the store's update URL; NativeMessagingAllowlist, with AgentGarm's host com.agentgarm.nm_host; QuicAllowed off, so the browser's HTTPS goes over TCP where AgentGarm's proxy governs it; and the extension's own on_secret: alert, block or redact. They come as a macOS profile, a Linux policy file, and a Windows .reg file with an administrative template for on_secret.

The extension asks the machine's agentgarmd for policy only when it is given that machine's node key, which differs on every machine: run fill.sh per machine with --node-pub and that machine's node.pub for its own node-key file, and with --host-path for the native-messaging host's manifest, which goes into the browser's native-messaging directory. Install the filled native-messaging/allowed-origins over the empty one in share/agentgarm/native-messaging/ beside AgentGarm's programs: the host answers only the extensions listed there, so without it the extension never gets the machine's policy. Without a node key, the managed on_secret decides. If you already set ExtensionInstallForcelist or NativeMessagingAllowlist elsewhere, add AgentGarm's entry to your own list: two profiles that set the same policy conflict.

share/agentgarm/mdm/fill.sh --out agentgarm-mdm --node-pub /var/lib/agentgarm/node.pub --host-path /usr/bin/agentgarm-nm-host

See also

Keep secrets and card numbers out of prompts

See which credentials your agent sends its model provider, have the proxy replace them with cache-safe placeholders, and deny tool calls that carry one.

3. Push the macOS profiles with Jamf or another MDM

Upload the filled profiles to Jamf, Intune, Kandji or any MDM and scope them to the Macs that get AgentGarm. agentgarm-system-extensions.mobileconfig approves AgentGarm's Endpoint Security and Network Extension system extensions, which users then cannot turn off; agentgarm-pppc-fda.mobileconfig grants Full Disk Access to the Endpoint Security extension and to /usr/local/bin/agentgarmd; agentgarm-transparent-proxy.mobileconfig configures the Network Extension's proxy; and agentgarm-pppc-airbag.mobileconfig grants Accessibility to the computer-use airbag, if you use it. Each grant is pinned to AgentGarm's signing identity, and each profile is system-wide and cannot be removed by the user.

Only a profile installed by MDM is binding; on an unmanaged Mac the user approves the extension in System Settings and grants Full Disk Access by hand. If one of these profiles is later removed, agentgarmd raises an alert and lowers every running task's assurance. The signed extensions need Apple's Endpoint Security entitlement, which is not granted yet, and whether the airbag's grant takes effect without a prompt has not been checked on a managed Mac.

See also

Govern computer-use agents

Let an agent drive your Mac's mouse and keyboard while AgentGarm's airbag drops its input on password managers, settings and other protected targets.

4. Install the package and start the services on each Mac

Deploy agentgarm-X.Y.Z-universal-apple-darwin.pkg as a package in your MDM. It puts AgentGarm.app, which carries both system extensions, into /Applications and the programs into /usr/local/bin, and runs no script, so nothing governs the Mac yet. Add macos-postinstall.sh from the tarball's share/agentgarm/mdm as a script your MDM runs as root after the package, with --agent for each agent whose managed hooks you want and --airbag if you use the computer-use airbag. It installs agentgarmd, the per-user session service, the hooks and the airbag, and agentgarm doctor reports the result.

The profiles only pre-approve the system extensions; macOS loads them when AgentGarm asks, and agentgarmd install asks, printing what macOS answered for each extension. The script exits with status 3 when everything else installed but the extensions are not active yet, for example because the profiles had not arrived, so your MDM shows it as failed and can run it again; every step is safe to repeat. This has not yet been tried on a Mac enrolled in an MDM, and the Endpoint Security extension waits on Apple's entitlement. Every macOS release is signed and notarised; until the first one is out, this step is for evaluation on Macs you control.

share/agentgarm/mdm/macos-postinstall.sh --agent claude-code --agent codex --airbag

5. Roll out to Linux with your configuration management

AgentGarm ships no Ansible role, Puppet module or Salt state: have your tool install the .deb or .rpm, then run the same commands as root, since the packages run no script either. Copy the browser policy files where the browsers read managed policy, /etc/opt/chrome/policies/managed/ for Chrome and /etc/opt/edge/policies/managed/ for Edge, with each machine's node-key file beside the fleet file, and the host manifest into /etc/opt/chrome/native-messaging-hosts/ or /etc/opt/edge/native-messaging-hosts/.

The node key exists only once agentgarmd has started on the machine, in /var/lib/agentgarm/node.pub, so fill each machine's node-key file after the services are installed.

sudo apt install ./agentgarm_X.Y.Z-1_amd64.deb
sudo agentgarmd install
sudo agentgarmd install --session
sudo agentgarmd hooks install claude-code

6. Deploy to Windows with Intune

preview

The Windows build is a preview and is not code-signed yet. The .msi installs per machine under C:\Program Files\AgentGarm and starts the AgentGarm service, but installs no agent hooks: run agentgarmd hooks install for each agent from an Intune script afterwards, as on macOS and Linux; AgentGarm also has a script that wraps it as an Intune Win32 app, but that script refuses an unsigned .msi, so an Intune rollout waits for signed releases.

For the extension, import the .reg files through Group Policy preferences, an Intune script or reg import, and the administrative template into Intune for on_secret; Chrome's and Edge's own templates already in Intune cover the force-install list. Chrome force-installs an extension only on a managed Windows machine: joined to a domain or to Entra ID, or enrolled in Chrome's cloud management. To remove AgentGarm, run agentgarmd uninstall before removing the package, so the agents' hooks come out first.

msiexec /i agentgarm-X.Y.Z-x86_64-pc-windows-msvc.msi /qn /norestart
agentgarmd uninstall
msiexec /x agentgarm-X.Y.Z-x86_64-pc-windows-msvc.msi /qn /norestart

7. Enrol each machine in Central Lite

Each enrolment token works once, on one machine, and expires within 24 hours, so deliver a separate token to each machine in a file only root can read, 0600 or 0400, and have your MDM or configuration management run agentgarm node enrol with --token-file as root. The command refuses a token file that another account owns or can read. Delete the file once the machine has enrolled.

sudo agentgarm node enrol --token-file /var/tmp/agentgarm-enrol-token

See also

Enrol developer machines

Enrol a machine in Central Lite with a one-time token that pins Central Lite's key, see it report in the inventory, and let its users enrol presence keys.