How to uninstall Amethyst on Mac

Amethyst is a tiling window manager that runs from the menu bar and needs Accessibility permission to move your windows. Its settings live in one preferences file, and if you wrote a YAML config file, that file overrides the settings window, so copy either one before removing Amethyst if you want the same layouts later. The steps below cover the official download from GitHub and the Homebrew cask amethyst.

Quit Amethyst and remove the app

Click Amethyst's menu bar icon and quit it from there, then move Amethyst from Applications to the Trash. The recorded test registered no login item; if you set Amethyst to start at login, check System Settings › General › Login Items & Extensions as well.

Where Amethyst keeps its data

In Finder, press Shift + Command + G and check each location that exists.

After backing up wanted settings and quitting Amethyst, move only unwanted items in the table to the Trash. The current cask additionally names ~/Library/Caches/com.amethyst.Amethyst, ~/Library/Cookies/com.amethyst.Amethyst.binarycookies and ~/Library/HTTPStorages/com.amethyst.Amethyst; open each exact location or its parent in Finder and remove only the named app item. For recent-document records, open ~/Library/Application Support/com.apple.sharedfilelist/com.apple.LSSharedFileList.ApplicationRecentDocuments and remove only existing com.amethyst.amethyst.sfl* files, keeping the shared parent.

Afterward, open System Settings › Privacy & Security › Accessibility and turn off or remove the entry for Amethyst; removing the app does not withdraw that permission on its own.

Check the result

pgrep -il amethyst
launchctl list | grep -i amethyst
ls -d ~/Library/Preferences/com.amethyst.Amethyst.plist ~/Library/Application\ Support/Amethyst ~/.amethyst.yml

• No output from pgrep means Amethyst is not running.
• No match after a successful launchctl list means no listed session label contains amethyst. Identify any matching job and check System Settings for a remaining Amethyst login item; this filter does not cover differently named jobs.
• ls -d printing "No such file or directory" for a path means that file or folder is gone; a printed path means it is still there.

If you installed it with Homebrew

Mole skips --zap when its list reaches unchecked or shared data, or cannot fully be checked, and still cleans the leftovers you selected.

The amethyst cask's zap list covers the preferences file and ~/Library/Application Support/Amethyst, plus the app's cache, cookies, HTTP storage and a recent-documents record, all under your own ~/Library. Mole lists those extra rows too and selects them by default when they exist. With “Remove data and settings with apps” off, ~/Library/Application Support/Amethyst stays unticked; turning it on can select this folder when it passes the app-data checks. Mole uses --zap only when the full removal list passes review. Running brew uninstall --cask --zap amethyst yourself trashes the whole list regardless of what Mole would tick; your YAML config is not in it.

brew uninstall --cask amethyst

What Mole lists

For an officially downloaded Amethyst:

• ~/Library/Preferences/com.amethyst.Amethyst.plist is selected by default.
• ~/Library/Application Support/Amethyst is listed for review. It stays unticked with “Remove data and settings with apps” off and can be selected with that setting on when it passes the app-data checks.
• The YAML config files are not listed.

What this test covered

Amethyst 0.24.3 was installed from its official GitHub release and uninstalled on September 25, 2026, with a development build of Mole. Accessibility permission was never granted in this run, so revoking it afterward was not observed, and no login item or launch agent appeared. The review row was ticked, and the app, its preferences, its Application Support folder and a temporary cache folder were trashed, with nothing from the list left on disk afterward. Amethyst