How to uninstall mmhmm on Mac
Before removing mmhmm, save and copy your presentation materials, recordings and locally stored work to a separate backup, then open the copy. This guide covers the official Mac download; Homebrew-specific removal is separate below.
This guide covers legacy mmhmm, not Airtime. The current vendor instructions describe Airtime system extensions and an Airtime virtual-camera menu, so those labels cannot be assumed to exist in mmhmm. If your legacy installation includes a camera, keep the app and its own uninstaller until that camera is removed using instructions for your installed product. Removing only the app is not proof the camera is gone. Account deletion and subscription cancellation are separate.
Quit and remove the app
Finish current work and quit mmhmm. Check Activity Monitor for its process before removing the app in Finder. In Applications, move mmhmm.app to the Trash; if you keep it elsewhere, use its actual location. Keep the Trash until your backup has been checked. Official documentation
Review local data
The locations below come from the test record or the live cask; their individual treatment is explained below. Open them through Finder’s Go › Go to Folder. Copy wanted contents first; leave them if you want to keep settings or cannot establish ownership. They are optional data removal, not a prerequisite for removing the app.
~/Library/Application Support/mmhmm
Check the result
This read-only check searches full process command lines, not disk contents.
pgrep -ifl 'mmhmm'
No output with exit status 1 means no matching command line was found. A printed entry needs inspection in Activity Monitor because names can match unrelated processes. An error is not proof of removal. Also check that the app is absent from its original Finder location; a retained data folder or independent component does not mean the app is still installed.
If you installed it with Homebrew
Use the installed cask receipt and uninstall without zap.
brew uninstall --cask mmhmm
Ordinary uninstall quits mmhmm and handles its package receipt. It does not by itself establish that legacy virtual-camera components have been removed. The live cask additionally names these zap targets, which can erase settings, local data or integration files; this is Homebrew’s list, not a vendor data-location claim.
~/Library/Application Support/mmhmm~/Library/Caches/app.mmhmm.hybrid~/Library/Caches/mmhmm~/Library/Preferences/app.mmhmm.hybrid.plist~/Library/Saved Application State/app.mmhmm.hybrid.savedState
This cask is disabled for new installation; that does not establish whether an existing receipt can be uninstalled on your Mac.
A direct brew uninstall --cask --zap mmhmm runs its own zap scope without consulting Mole’s checkboxes. Mole uses zap only when the complete scope passes its gate; unchecked or shared paths, paths outside the review boundary, unknown stanzas and unsupported directives suppress it. Selected remnants still use Mole’s deletion path.
What Mole lists
~/Library/Application Support/mmhmm is listed for review and is not selected by default. Bundle-identity preferences and caches are normally selected by default when present. The application-payload record establishes no virtual-camera protection or removal result.
These defaults assume “Remove data and settings with apps” is off. Opting in also selects eligible reviewed app data; shared stores and protected data retain individual review or stay locked.
What this test covered
The September 21, 2026 record covers the following test. Only the legacy mmhmm application payload was copied from the official package. No virtual-camera installer or helper was run. Its app and the explicitly selected support folder were removed. Virtual camera removal, a complete package installation and Airtime were not tested.