Skip to main content

​
Overview

Jamie for macOS is deployed as a signed and notarized per-machine PKG. It installs Jamie.app into /Applications for all users on the Mac, together with a background update daemon (com.jamie.updater) that keeps the app up to date.
The update daemon handles all version management, so your MDM should only handle the initial deployment — not ongoing version updates.

​
Download

Download the enterprise PKG

Jamie.pkg
The PKG is a universal build that runs natively on Apple silicon and Intel Macs. It requires macOS 14.2 or later.

​
Package details

​
Adding the app to your MDM

Upload Jamie.pkg as a standard package and scope it to the target computers. No pre- or post-install scripts are required on your side; the PKG starts the update daemon itself.
1

Upload the package

Go to Settings → Computer management → Packages → New and upload Jamie.pkg.
2

Create a policy

Go to Computers → Policies → New, add the package with the Install action, and set the execution frequency to Once per computer.
3

Scope the policy

Scope it to the computers or smart groups that should get Jamie.
Don’t add Jamie to Jamf Patch Management or App Installers — those would compete with the built-in updater.

​
Don’t enforce the app version

Jamie updates itself in the background. If your MDM enforces the originally deployed version, it fights the updater:
1

Your MDM deploys version X

2

The Jamie update daemon updates to version Y

3

The MDM detects a version mismatch and reinstalls version X

4

The daemon updates again — creating an endless reinstall loop

Configure your MDM to only check that Jamie is installed — in Intune, set Ignore app version = Yes; in Jamf, install once per computer and leave the app out of patch management. Re-running an older PKG is harmless: it doesn’t replace a newer Jamie.app that’s already installed.

​
What the PKG installs

The update daemon starts right after installation, so updates work without a reboot or user login.

​
Automatic updates

Jamie checks for new versions in the background and installs them automatically. It needs no user interaction and no admin rights from the user.
  • Updates are verified. Only packages signed by Jamie and approved by Apple are installed.
  • Meetings aren’t interrupted. If a meeting is being recorded, the update waits until it’s finished.
  • Jamie reopens afterwards. If the app was open before the update, it’s reopened once the update completes.

​
Network requirements

The daemon makes outbound HTTPS requests only: See Firewall & ports for the full list of endpoints the app uses.

​
Verifying the installation

Run these in Terminal on a target Mac:
The log file rotates at 5 MB; the previous log is kept as updater.log.bak.

​
Uninstall

Remove the app and the daemon with:
If only Jamie.app is deleted, the daemon notices that the app is missing and removes itself after 24 hours, so it never reinstalls an app you’ve removed.

​
Notes

  • Do not let your MDM manage Jamie’s version (patch management, auto-update catalogs, version-enforced app records) — the built-in update daemon handles all version management.
  • Re-deploying the same PKG is safe and non-destructive.
  • Users still grant Jamie’s macOS privacy permissions (such as microphone access) on first launch, exactly as with the standard app.
  • Deploying Jamie on Windows? See the Intune MSI Deployment Guide.
Last modified on October 27, 2026