Jamf Binary Runtime

Paste one command into a Jamf policy set to run daily. No script to write.

Before you begin

Admin access to Unbound and Jamf Pro.
macOS 13 or later, 300 MB free. Older Macs use the Python installer.
HTTPS allowed to getunbound.ai, unbound-release-artifacts.s3.us-west-2.amazonaws.com, and the hosts after --backend-url and --gateway-url in your command.

1. Copy the command

Sign in to your Unbound dashboard and open Configure — on a dedicated deployment that is your own address, not gateway.getunbound.ai. Select My org (MDM), then the macOS tab, and copy the command. It looks like this, with your own key and URLs:

sudo bash -c "$(curl -fsSL https://getunbound.ai/setup/mdm/onboard.sh)" -- --api-key YOUR_ADMIN_API_KEY --backend-url https://backend.getunbound.ai --gateway-url https://api.getunbound.ai --backfill

YOUR_ADMIN_API_KEY is your admin API key: one key covers the whole fleet, and each Mac uses it to fetch its own device key. It arrives filled in, so paste the command exactly as copied.

If the command starts with sudo python3, follow the Python installer page instead.

2. Create the policy

Computers → Policies → New

General

Name it Unbound daily onboard, tick Enabled, set Trigger to Recurring Check-in and Execution Frequency to Once every day.

Files and Processes

Select Files and Processes → Configure, then paste the command into Execute Command as a single line.

Scope

Add one test Mac, then Save.

Anyone who can open the policy can read the API key it contains, so limit who can edit policies in Jamf.

3. Test, then roll out

On the test Mac, run sudo jamf policy -id POLICY_ID, where POLICY_ID is the number after id= in the policy’s URL. The first run takes a few minutes and ends with unbound-hook setup summary, every tool marked configured. Then confirm both:

Jamf

Computers → [the Mac] → History → Policy Logs shows Completed.

Unbound

In your Unbound dashboard, the Mac appears under Settings → Devices, and its Last Sync on AI Tools Discovery is recent.

When both pass, change the policy’s scope to your developer Mac group. To re-test the same day, open the policy’s Logs and select Flush.

Command flags

You do not need to edit the command. This is what it carries.

Flag	Purpose	Default
`--api-key <key>`	Your admin API key. Required unless `--clear`	—
`--backend-url <url>`	Where setup results and scans are reported	`https://backend.getunbound.ai`
`--gateway-url <url>`	The AI gateway the installed tools point at	`https://api.getunbound.ai`
`--frontend-url <url>`	Your dashboard host, written into each user’s config	Unbound’s dashboard
`--backfill`	Import past Claude Code, Codex and GitHub Copilot sessions	off
`--skip-managed-settings`	Claude Code only: install the hook, leave its managed settings to you. See Tamper Resistance	off
`--clear`	Remove Unbound. Needs no key and no URLs	—

Troubleshooting

A failed run prints UNBOUND_INSTALL_FAILED step=<step> code=<n> in the policy log.

Symptom	Fix
`Could not download the installer`	Allow `getunbound.ai` through your proxy, including TLS inspection.
`artifact host unreachable`	Allow `unbound-release-artifacts.s3.us-west-2.amazonaws.com`.
`step=verify_sha256` or `pkg Team ID mismatch`	A proxy altered the package. Exclude the artifact host from TLS inspection.
`macOS <n> < required 13`	Use the Python installer on that Mac.
`401` or `403`	The key was rotated. Copy the command from Configure again.
A tool shows `deferred`	The reason is printed beside it. Other tools still configured; the next run retries.

Remove Unbound

Disable the policy or remove the Macs from its scope, then run:

sudo bash -c "$(curl -fsSL https://getunbound.ai/setup/mdm/onboard.sh)" -- --clear

It prints UNBOUND_CLEAR_OK. To also delete what it leaves behind:

sudo rm -rf "/Library/Application Support/Unbound" /var/log/unbound
for home in /Users/*; do sudo rm -rf "$home/.unbound"; done

Deploy the package from your own Jamf

Use this when your security policy does not allow downloading software at install time. You verify the signed package once and host it in Jamf. Macs download nothing from Unbound when they install it.

Download

From the latest release, download unbound-runtime-<version>.pkg, unbound-runtime-<version>.pkg.sha256, jamf-setup.sh and jamf-setup.sh.sha256.

Verify the downloads

pkgutil --check-signature unbound-runtime-<version>.pkg
spctl -a -vv -t install unbound-runtime-<version>.pkg
shasum -a 256 unbound-runtime-<version>.pkg
cat unbound-runtime-<version>.pkg.sha256
shasum -a 256 -c jamf-setup.sh.sha256

The signature must read Developer ID Installer: Websentry Inc (ZMA55FTA8W) and Notarization: trusted by the Apple notary service. spctl must print accepted and source=Notarized Developer ID. These two checks prove the package comes from Unbound unmodified. The hash files come from the same release, so they only catch a corrupted download: the two package hashes must match, and the script check must print jamf-setup.sh: OK.

Upload to Jamf

In Settings → Computer management → Packages, upload the package. In Settings → Computer management → Scripts, create a script named Unbound setup and paste the contents of jamf-setup.sh. Read it before you upload it. That is how you confirm the script, since its hash file comes from the same release. It is short, runs the installed runtime and downloads nothing. Its only network call reports the install result to your backend.Wait until the package no longer shows Availability pending before you run the policy. If it stays pending for more than an hour, delete it and upload it again.

Create the policy

Computers → Policies → New. Set Trigger to Recurring Check-in and Execution Frequency to Once per computer. Add the package with the Install action. Add the Unbound setup script with Priority set to After, and fill in its parameters from the command in Configure:

Parameter	Value
4	Your admin API key
6	The `--backend-url` value
7	The `--gateway-url` value
9	`backfill` to import past Claude Code, Codex and GitHub Copilot sessions, otherwise empty
10	`skip-managed-settings`, otherwise empty
11	The `--frontend-url` value, if your command has one

Leave 5 and 8 empty. Test on one Mac as in step 3.

Jamf stores the API key in the policy and passes it to the script on each Mac, so anyone who can view the policy can read it. Limit who can view and edit policies in Jamf.

To repair tool settings every day the way the curl command does, add a second policy with only the Unbound setup script, the same parameters, and Once every day. Macs installed this way do not update on their own. When a new release ships, verify the new package, replace it in the policy, and Flush the policy logs so each Mac installs it once. To remove Unbound, run the Unbound setup script with parameter 8 set to clear. No key is needed. It prints UNBOUND_CLEAR_OK.

What gets installed

Before installing, the installer checks the package against a pinned SHA-256 hash and confirms it is signed by Unbound’s Developer ID, Team ID ZMA55FTA8W.

Files and services on each Mac

Path	Purpose
`/opt/unbound/<version>/`	The runtime. `/opt/unbound/current` points to the active version. The previous version is kept for rollback.
`/Library/LaunchDaemons/ai.getunbound.discovery.plist`	AI tool discovery service
`/var/log/unbound/`	`discovery.log` and `discovery.err.log`, rotated at 5 MB with five compressed generations kept
`/Library/Application Support/ClaudeCode/managed-settings.json`	Claude Code hooks, merged into any existing settings
`/Library/Application Support/Cursor/hooks.json`	Cursor hooks
`/Library/Application Support/GitHubCopilot/managed-settings.json`	Copilot telemetry settings
`/etc/augment/settings.json`	Augment Code hooks, merged into any existing settings
`~/.codex/hooks.json` and `~/.copilot/hooks/unbound.json`	Codex and Copilot hooks, per user
`~/.unbound/config.json`	Device key and your Unbound URLs, per user

The discovery service scans the Mac on install and every twelve hours after that. Confirm it is running with sudo launchctl print system/ai.getunbound.discovery.The package receipt is ai.getunbound.runtime. Use it to build a Jamf Smart Group, or run pkgutil --pkg-info ai.getunbound.runtime to check the installed version.

Tamper Resistance

Keeping Unbound active on every device with managed settings.

Getting Started

CLI

Policies

Analytics

Integrations

MDM Integrations

Connections

Support & Troubleshooting

Before you begin

1. Copy the command

2. Create the policy

3. Test, then roll out

Jamf

Unbound

Command flags

Troubleshooting

Remove Unbound

Deploy the package from your own Jamf

What gets installed

Tamper Resistance

​Before you begin

​1. Copy the command

​2. Create the policy

​3. Test, then roll out

Jamf

Unbound

​Command flags

​Troubleshooting

​Remove Unbound

​Deploy the package from your own Jamf

​What gets installed

Tamper Resistance

Before you begin

1. Copy the command

2. Create the policy

3. Test, then roll out

Command flags

Troubleshooting

Remove Unbound

Deploy the package from your own Jamf

What gets installed