How to uninstall Conductor on Mac
Save and back up each Conductor workspace, including uncommitted and untracked files, before removing the Mac app. The official worktree guide explains that workspaces have separate checkouts but share Git repository data. This page covers the desktop app, not deletion of cloud workspaces.
Quit and remove the app
Finish or stop workspace commands and agent jobs, then quit Conductor with Cmd + Q. Check the actual executable for any surviving process before moving Conductor.app to the Trash. Keep repositories and separate coding-agent installations.
Review local data
After jobs have stopped and Conductor has quit, open the three exact Library folders below with Finder Shift + Command + G. Copy wanted configuration/history outside the folder before removal, then move only the folders you chose to remove to the Trash. Skip missing paths and leave project worktrees and system WebKit temporary state alone.
~/Library/Application Support/com.conductor.appheld local application data in the test. Copy wanted configuration or history before removal; the exact-ID directory is selected by default.~/Library/Caches/com.conductor.appand~/Library/WebKit/com.conductor.appwere attributable cache and web state.- Projects, Git worktrees and their untracked files need their own backup. A branch or remote copy alone does not preserve every local file.
- System-owned WebKit temporary directories were intentionally left outside the removal list.
Check the result
pgrep -ifl Conductor
ls -ld /Applications/Conductor.app "$HOME/Library/Application Support/com.conductor.app" "$HOME/Library/WebKit/com.conductor.app"
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. Zap names the exact support, cache and WebKit directories above. It does not act as a cloud-workspace or repository-deletion command.
To uninstall without zap, use:
brew uninstall --cask conductor
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 conductor runs Homebrew’s full zap list without consulting Mole’s checkboxes.
Accounts and cloud workspaces
Removing the Mac app does not cancel a subscription or delete a hosted workspace. Manage those separately in the service.
What Mole lists
Mole selects the app, exact-ID support directory and attributable caches by default. Leave the support directory unchecked if you want its local state. Independently stored repositories and protected system WebKit state are not blanket uninstall targets.
What this test covered
On September 25, 2026, Conductor 0.87.4 was copied from the official Mac archive and uninstalled using a development build of Mole. Ten recorded items reached the Trash; protected WebKit temporary state was skipped. The app exited before a Status row could be verified, so Status remained unverified. Active agents, populated workspaces and cloud deletion were not tested.