Deploy to a Mac Fleet (MDM)
You push a signed installer and a small set of configuration profiles from your MDM. Each Mac then enrolls, installs the browser extension and the coding-agent hooks, and starts reporting — no action from the user on a supervised Mac.
What you deploy
All of these are on Endpoints → Setup in your workspace, generated for your workspace.
| Artifact | Required? | What it does | |
|---|---|---|---|
| 1 | Base profile (waxell.mobileconfig) | Required | Trusts your workspace certificate, pre-approves the Waxell system extensions, and delivers the enrollment key. |
| 2 | The app (WaxellSetup-arm64.pkg) | Required | Installs the Waxell agent, registers the managed hooks for coding agents, and registers the browser bridge. Signed with Developer ID and notarized by Apple. |
| 3 | Browser AI profile | Recommended | Force-installs the Waxell browser extension into Chrome, Edge and Firefox and configures it. This is what turns on browser capture. |
| 4 | Flow visibility profile | Optional | Turns on the network content filter, which records which app reached which AI host (metadata only) and enforces site and app blocks. |
The base and browser profiles contain your workspace's enrollment key. Store them like any other credential.
The profiles are emitted unsigned; your MDM signs them on upload, which is the normal flow.
Identifiers (for allow-lists and EDR exclusions):
| Value | |
|---|---|
| Team ID | 2RWC9968XY |
| App | dev.waxell.setup |
| Content filter extension | dev.waxell.setup.flowmonitor |
| Network extension (legacy) | dev.waxell.setup.proxymonitor |
| Browser extension (Chrome) | npipfngnlpinjdbbdoihdoihfhpmibef |
| Browser extension (Edge) | egoiaobngfnpdbnpkeofaogmfohpoffc |
| Browser extension (Firefox) | waxell-ai-monitor@waxell.dev |
Step 1 — Download
From Endpoints → Setup, download the base profile, the .pkg, the browser
AI profile and, if you want network metadata and site blocking, the flow
visibility profile.
Step 2 — Upload to your MDM
Upload each .mobileconfig as a custom profile and the .pkg as an enterprise
app:
| MDM | Profiles (.mobileconfig) | App (.pkg) |
|---|---|---|
| Jamf Pro | Computers → Configuration Profiles → Upload | Computers → Packages, then a Policy with an Install package action |
| Kandji | Library → Add → Custom Profile | Library → Add → Custom App (installer package) |
| Intune | Devices → Configuration → Create → macOS → Templates → Custom | Apps → macOS → Add → macOS app (PKG) |
| Hexnode | Policies → New Policy → macOS → Custom Configuration | Apps → +Add → macOS → Enterprise App |
Step 3 — Target a group and push
Assign every artifact to the same device group. Order does not matter.
On supervised Macs (enrolled through Apple Business Manager / Automated
Device Enrollment) the system extensions and content filter turn on silently.
On Macs enrolled by hand, the user must approve the network extension once in
System Settings → General → Login Items & Extensions. Check with
profiles status -type enrollment.
Step 4 — Verify
Within a few minutes each Mac appears in your workspace:
- Health — the device reports in every 60 seconds. Hooks should read managed, and Capture reads on once someone uses AI in a browser.
- Inventory → AI Apps — the AI apps found on the device.
- Activity and Captures — AI use as it happens.
On the Mac itself, sudo profiles list -all | grep -i waxell lists the installed
profiles. Seeing the system extension as activated (systemextensionsctl list)
does not prove the content filter is configured; the flow visibility profile
does that.
Without an MDM: RMM deployment
NinjaOne, Kaseya, Datto, Atera, Addigy and similar RMMs can deploy the agent with
the script shown on Endpoints → Setup. It installs the .pkg, enrolls the
device for the logged-in user, and force-installs the browser extension. It
cannot approve the network extension — that still needs a configuration profile
or a click from the user — and it needs a user logged in at the console.
Optional: turn off encrypted DNS in browsers
Browsers using DNS-over-HTTPS hide which AI sites they reach from the network monitor. Browser capture is unaffected (the extension sees the page), but if you rely on flow visibility, push the Disable DoH profile from Setup. The Health page warns per device when DoH is on.
Uninstalling
Remove the Waxell profiles and the app in your MDM. Removing the app does not clear every background service, managed hook registration and system extension on its own; contact Waxell support for the uninstall script, which removes all of them (system extensions finish removing at the next restart).