How to uninstall CodexBar on Mac

Save wanted settings before removing CodexBar. It displays usage from other services; uninstalling it does not cancel their subscriptions and should not remove other AI tools’ conversations or projects.

Quit and remove the app

Quit from CodexBar’s menu. For a website download, move CodexBar.app from Applications to Trash. For a Homebrew installation, use the next section so its managed command-line link is handled too.

If you installed it with Homebrew

brew uninstall --cask codexbar

The inspected steipete/tap/codexbar cask links the app’s CodexBarCLI as codexbar. Ordinary cask removal also removes that managed link, rather than only the app. A separate formula or manually copied CLI is outside that scope. Check the channel with brew list --formula codexbar; run brew uninstall --formula codexbar only if that separate formula is installed and you also want it removed.

Omitting --zap retains the zap-listed data. Adding zap directly targets locations including ~/Library/Application Support/CodexBar, ~/Library/Application Support/com.steipete.codexbar, app and widget containers, preferences and caches, without consulting Mole’s checkboxes. The cask’s declared group name may differ from the installed group; do not guess additional containers to delete.

Mole uses zap only when the entire scope passes review. Unchecked, shared or out-of-boundary paths suppress zap; selected entries can still use Mole’s own removal flow.

Review settings and shared data

Inspect these locations individually with Shift + Command + G in Finder, copying wanted settings elsewhere first. They were observed locally and need not exist in every version.

Check the result

if [ -e "/Applications/CodexBar.app" ]; then
  printf '%s\n' 'App bundle still exists'
else
  printf '%s\n' 'App bundle not found at this path'
fi
command -v codexbar
ls -ld "$HOME/.codexbar" "$HOME/.config/codexbar"
ls -ld "$HOME/Library/Group Containers/Y5PE65HELJ.com.steipete.codexbar" "$HOME/Library/Application Scripts/Y5PE65HELJ.com.steipete.codexbar"

Output from command -v identifies a surviving command; no output only means the current PATH cannot find it. An ls listing means a directory remains, No such file means it is absent, and Permission denied leaves it unverified. A retained protected container does not mean the app is running.

What Mole lists

Identified caches, preferences, the app’s own widget container and ~/Library/Application Support/com.steipete.codexbar are selected by default; these can include settings. With app-data selection off, ~/.codexbar and ~/Library/Application Support/CodexBar are listed but not selected.

Before deleting an App Group, Mole also checks whether other installed apps claim it. An incomplete ownership check retains the group. The test removed ~/.config/codexbar separately through Finder; this is not evidence of automatic Mole coverage for that directory.

What this test covered

The installed CodexBar 0.70.0 was uninstalled on October 8, 2026. Mole removed the app and 15 of 17 selected remnants. Status identified one app row and update detection identified Homebrew. The two App Group paths above remained because their ownership check was incomplete, so this was not a complete data wipe. The explicitly disposable ~/.config/codexbar directory was then removed through Finder, and the current PATH no longer resolved codexbar. Other tools’ accounts and conversations were not removed.