How to uninstall Jamie on Mac

Save wanted Jamie meeting notes and transcripts and check the saved copies before removing the Mac app. Finish any active capture first. The official site describes on-device meeting capture; app removal is separate from removing online reports or cancelling a plan.

Quit and unload the local startup job

Quit Jamie from its own app. The local test found ~/Library/LaunchAgents/Jamie.plist with the service label Jamie. If that file exists, inspect it first and confirm its program belongs to your Jamie installation:

plutil -p "$HOME/Library/LaunchAgents/Jamie.plist"

A missing file needs no removal. If it points to something else or cannot be read, leave it and stop this service-removal step. For the confirmed Jamie job, the next command targets only that service in your own login session; id -u supplies your user ID:

launchctl bootout "gui/$(id -u)/Jamie"

A successful bootout unloads that registration. If it reports the service is absent, confirm that with the read-only print command below before proceeding; permission or other errors leave this step unconfirmed.

After the job is confirmed unloaded, copy wanted local contents from ~/Library/Application Support/com.jamie.app or ~/Library/Application Support/jamie while the app is closed. Check the backup, then move the app and its confirmed ~/Library/LaunchAgents/Jamie.plist to the Trash in Finder. Keep other launch agents and original meeting documents.

If you installed it with Homebrew

Keep the app available until managed removal completes:

brew uninstall --cask jamie

The current cask unloads the Jamie job during ordinary removal. Its additional zap targets are ~/Library/Application Support/com.jamie.app, ~/Library/Application Support/jamie, ~/Library/Caches/com.jamie.app, ~/Library/HTTPStorages/com.jamie.app.binarycookies, ~/Library/LaunchAgents/Jamie.plist and ~/Library/WebKit/com.jamie.app. Direct brew uninstall --cask --zap jamie uses the whole list independently of Mole’s checkboxes. Keep no-zap removal when retaining data; Mole only uses zap when its complete scope passes selection and shared-data checks, otherwise selected remnants use its own removal flow.

Check the result

launchctl print "gui/$(id -u)/Jamie"
ls -ld "$HOME/Library/LaunchAgents/Jamie.plist"

A printed job is still registered; a service-not-found message concerns only that label. A listed plist remains and can be loaded later, even if the current job is absent. Permission or other errors leave the step unconfirmed. Check the app’s actual Finder location too; these checks do not verify online reports.

What Mole lists

The selected app is included for removal. Exact app support ~/Library/Application Support/com.jamie.app is normally selected when present and unprotected; the display-name ~/Library/Application Support/jamie is reviewed and unchecked by default. A launch agent whose program points inside the selected app is selected by default, while a name-only match requires review. Remove data and settings with apps is off by default; opting in includes eligible reviewed data with shared and protected items retaining their boundaries.

What this test covered

The copied official app was removed with a source-built Mole on September 22, 2026. The first attempt was skipped while Jamie was running; retry after its process exited removed the app and the observed launch-agent plist, and the job was absent afterward. Meeting capture, populated report recovery, account cancellation and a Homebrew-managed uninstall were not tested.