How to uninstall Goose on Mac
Keep your Goose sessions, recipes and configuration before uninstalling the desktop app. The official project site offers both a desktop app and CLI, and the local test found shared configuration and session directories. Removing Goose.app does not make the CLI or its data disposable.
Quit and remove the app
Stop running agent tasks and quit Goose with Cmd + Q. Check that the bundled helper processes have stopped, then move Goose.app to the Trash. Keep any independently installed goose command and projects unless you are separately retiring them.
Review local data
After stopping Goose tasks and quitting, open ~/Library/Application Support/Goose with Finder Shift + Command + G. Copy wanted desktop data outside this folder, then move only this folder to the Trash if you no longer need it. Skip it if missing, and keep the shared configuration, session and state roots below while an independently installed CLI still uses them.
~/Library/Application Support/Goosecontains desktop data and cache subfolders; copy needed material before deleting the parent.~/.config/gooseheld configuration and OAuth material in the local test.~/.local/share/gooseheld shared sessions, and~/.local/state/gooseheld runtime state. These are separate from a desktop-only uninstall. Do not purge provider keys or every Goose folder by name.
Check the result
pgrep -ifl goose
command -v goose
ls -ld /Applications/Goose.app "$HOME/Library/Application Support/Goose" "$HOME/.config/goose" "$HOME/.local/share/goose"
No process output means this name was not found, not that every helper has gone. Check any match against the app’s actual executable path. A missing-path error from ls means only that location is absent; permission errors leave its state unknown. A surviving folder can be intentional data to keep.
Output from command -v shows a CLI still reachable through your PATH; no output does not prove that every independently installed copy is gone.
If you installed it with Homebrew
The cask token is block-goose. It has no separate uninstall helper and zaps only ~/Library/Application Support/Goose; the independently installed CLI and shared home-data roots are not in this zap list.
To uninstall without zap, use:
brew uninstall --cask block-goose
Mole checks Homebrew's full removal list and skips --zap when it reaches unchecked data, shared files or anything it cannot verify. It still removes the leftovers you selected. A direct brew uninstall --cask --zap block-goose runs Homebrew’s full zap list without consulting Mole’s checkboxes.
Removing Goose does not cancel a model-provider subscription or erase data already sent to that provider. Provider billing and remote data are separate.
What Mole lists
Mole selects the app, attributable preferences and reviewed regenerable Electron cache leaves by default. ~/Library/Application Support/Goose is listed for review: with Default remove app data off it starts unchecked; with it on, eligible own data can start checked. Uncheck it to retain desktop data. Normal desktop uninstall does not claim the Goose CLI’s shared configuration, session and state roots; the separate AI data page is a different review surface.
What this test covered
On September 25, 2026, the official Goose 1.52.0 app was copied from its archive and uninstalled with a development build of Mole. Ten selected items were removed. The configuration, share-data and state roots remained by design because of CLI/shared ownership. Provider sign-in, real sessions, a CLI uninstall and the published Mole package were not verified.