How to uninstall Supacode on Mac
Back up Supacode settings and every worktree with wanted changes before removing the app. The official storage guide places managed worktrees inside the same hidden directory as settings. This page covers the official Mac app copied from its disk image, not the coding agents it launches.
Quit and remove the app
Stop running agent tasks and terminal commands, save project changes, then quit Supacode with Cmd + Q. Move supacode.app from Applications to the Trash after checking the backup. Keep the repositories and separately installed agent CLIs.
Review local data
After stopping jobs, checking backups and quitting, open the exact Library paths below with Finder Shift + Command + G and move only the data you no longer need to the Trash. Skip missing paths and leave shared parent folders alone. Keep ~/.supacode while any wanted managed worktree remains inside it. If you have preserved the needed files and Git state outside it and no longer need any worktree there, open ~ with Finder Go to Folder, press Shift + Command + . to show hidden items, and move only .supacode to the Trash. Linked worktrees share repository metadata, so copying their files alone does not preserve the Git relationship; use Git's documented worktree move/repair process when retaining a worktree elsewhere. Git worktree documentation
~/.supacodecontains settings and local UI state. Current documentation also puts managed worktrees under~/.supacode/repos; copy wanted files and preserve their Git relationship before considering the parent directory for removal.~/Library/Application Support/app.supabit.supacodeand~/Library/Preferences/app.supabit.supacode.plistheld app-local settings in the test. Copy wanted configuration first.~/Library/Caches/app.supabit.supacode,~/Library/Caches/SentryCrash/Supacode,~/Library/HTTPStorages/app.supabit.supacodeand~/Library/HTTPStorages/app.supabit.supacode.binarycookieswere attributable app caches and web state.- The tested app added conditional managed hooks to
~/.codex/hooks.json. They were retained after uninstall and only run in a Supacode surface; do not delete this shared file or other Codex history to remove the app.
Check the result
pgrep -ifl supacode
ls -ld /Applications/supacode.app "$HOME/.supacode" "$HOME/Library/Application Support/app.supabit.supacode"
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.
If you installed it with Homebrew
The cask has no separate uninstall helper. Its zap list covers exact support, cache, HTTP storage, cookies and preferences; it does not include ~/.supacode or remove the shared Codex hooks.
To uninstall without zap, use:
brew uninstall --cask supacode
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 supacode runs Homebrew’s full zap list without consulting Mole’s checkboxes.
What Mole lists
Mole selects the app, exact bundle-ID support directory, preferences and attributable caches by default. It lists ~/.supacode for review: with Default remove app data off it starts unchecked; with it on, eligible own data can start checked. That parent may contain worktrees, so inspect and uncheck it until wanted files and Git state are safely preserved; removing the app does not require removing it.
What this test covered
On September 25, 2026, Supacode 0.10.8 was copied from the official Mac package and tested with a development build of Mole. The first pass missed ~/.supacode; an exact reviewed leaf was added and its removal was recorded on retest. The run did not validate active agent jobs, provider operations or recovery of populated worktrees.