How to uninstall Atoll on Mac

Atoll is a free, open-source app that puts a Dynamic Island on the MacBook notch, from getatoll.app and its GitHub project. Its README lists a clipboard history, a Shelf for files, timers and calendar previews, but does not say where any of that is stored, and the test found no folder of its own for it. If you used the clipboard history or Shelf, look inside Atoll before you quit it and copy out what you need; once it is removed the app cannot show you what was there. This guide covers the disk image from the project's GitHub release and the Homebrew cask atoll.

Quit and remove the app

1. Open Atoll and copy out any clipboard entry or Shelf file you still need.
2. Quit Atoll from its menu bar icon, or press Command + Q while it is frontmost. In the test it ran as one row with 3 processes in Mole's Status page. The test registered no login item or launch agent; if you turned on a start-at-login option, check System Settings › General › Login Items & Extensions.
3. Open Finder, go to Applications and drag Atoll to the Trash.
4. Open System Settings › Privacy & Security and remove Atoll from the lists you granted it: the README names Accessibility, Camera, Calendar, Screen Recording and Music. Mole does not change these lists.

Where the data lives

Press Shift + Command + G in Finder to open each path. Skip any path that is not on your Mac.

Check the result

pgrep -il Atoll
ls -d /Applications/Atoll.app "$HOME/Library/Preferences/com.Ebullioscopic.Atoll.plist" "$HOME/Library/Caches/com.Ebullioscopic.Atoll" "$HOME/Library/HTTPStorages/com.Ebullioscopic.Atoll"
ls -d "$(getconf DARWIN_USER_CACHE_DIR)com.Ebullioscopic.Atoll"

• No output from pgrep means Atoll is not running. A printed line is a process still alive; quit it first.
• For ls -d, No such file or directory means that path is gone, which is the usual result for the three ~/Library paths. A printed path is still on disk. A preferences file can be written again as the app quits, so check after it has quit.

If you installed it with Homebrew

brew uninstall --cask atoll

The cask quits Atoll and removes the app. Its zap list trashes the cache, HTTP storage and preferences paths in the table above, and nothing else. A direct brew uninstall --cask --zap atoll runs that list and does not read Mole's checkboxes. Mole adds --zap only when its whole removal scope passes its zap gate (unchecked or shared paths, paths outside the reviewed boundary, unknown stanzas or unsupported directives suppress it) and otherwise removes the rows you selected itself. The Homebrew install was not tested.

What Mole lists

Mole selects the app and the temporary cache row, and the three ~/Library paths above when they exist. Status shows Atoll as one row, and the update page reads the project's Sparkle feed.

What this test covered

On November 9, 2026, Atoll-2.3.3.dmg (Universal) from the project's GitHub release, whose checksum matched the Homebrew cask, was copied to Applications on a test Mac without running brew install and opened once. It was removed with a source-built Mole with every review row ticked. Mole asked the app to quit, force quit it when it kept running, and moved the app and 1 row (the temporary cache) to the Trash with no failures; a rescan then found nothing left. Status showed one row with 3 processes, and Mole found a Sparkle feed; no update was run. No permission was granted and no clipboard entry, Shelf file or timer was created, so where Atoll keeps those was not tested, nor were the Homebrew install and Mole's notarized release build.