How to uninstall Commander One on Mac
Finish transfers and save wanted connection settings before uninstalling Commander One. Files in its panels, on remote servers or in cloud accounts are separate from the app. This guide covers the official Mac app and the commander-one Homebrew cask, not the App Store build.
Finish transfers and quit
Wait for wanted copy, move and upload operations to finish, and open the destination files to confirm them. The official Connections Manager guide places saved remote connections under Window › Connections Manager. Keep the information needed to reconnect before resetting app data.
Quit Commander One with Cmd + Q, then move Commander One.app from Applications to Trash. Avoid using the app's own Delete key to remove it: the Preferences guide explains that this can permanently delete files when Move to trash is disabled.
Review settings separately from your files
After finishing transfers, saving connection information and quitting Commander One, press Shift + Command + G in Finder to open the locations below. Back up wanted settings, then move only confirmed Commander One items you choose to remove to Trash. Keep activation or connection files whose ownership is uncertain, and leave vendor parent folders intact.
| Location | Keep or remove |
|---|---|
| ~/Library/Application Support/com.eltima.cmd1 | App support data. Back up wanted configuration before removal. |
| ~/Library/Preferences/com.eltima.cmd1.plist | Commander One preferences. Keep for reinstalling with the same setup. |
| ~/Library/Caches/com.eltima.cmd1 and ~/Library/HTTPStorages/com.eltima.cmd1 | App cache and web state. Review after quitting. |
| ~/Library/Logs/CommanderOne.log | The app log observed in the uninstall test. |
| ~/Library/Preferences/com.eltima.activator.xml | Activation-related file in the cask and old test. Keep unless its ownership is confirmed. |
The current cask also names com.eltima.TCXDropboxFS.plist, com.eltima.TCXFtpFS.plist, com.eltima.TCXGDrive.plist and com.eltima.TCXWebDAVFS.plist under ~/Library/Preferences, plus ~/Library/Saved Application State/com.eltima.cmd1.savedState. Keep needed connection settings, and do not delete every Electronic Team preference or a shared vendor folder. Removing this app does not delete a cloud account or cancel another service's subscription.
Check the result
pgrep -ifl 'Commander One'
ls -ld '/Applications/Commander One.app' "$HOME/Library/Application Support/com.eltima.cmd1" "$HOME/Library/Preferences/com.eltima.activator.xml"
No process output means no matching name is running. Printed paths remain, missing-path errors mean absence, and permission errors leave the result unknown. Confirm your saved files and remote destinations separately.
If you installed it with Homebrew
brew uninstall --cask commander-one
This uninstalls the cask without zap. A direct brew uninstall --cask --zap commander-one also removes every support, cache, web-state, preference and saved-state location in the cask above, including the activator and connection preferences, regardless of Mole's checkboxes.
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.
What Mole lists
Exact bundle-owned support data, preferences, caches and web state are selected by default when present. Back up or uncheck support data you want to keep. Additional cask-derived paths are review rows unless Mole independently attributes them more strongly; with Remove data and settings with apps off they are unchecked, and enabling it can preselect eligible app-specific data. Shared activation and connection settings still need an ownership check. Keep those files unchecked when ownership is uncertain.
What this test covered
Commander One 3.17.1 was copied from the official package into Applications and removed on September 21, 2026, without a Homebrew receipt. The app, preferences, caches, HTTP storage and Logs/CommanderOne.log went to Trash after reviewing the listed items. A 4 KB Preferences/com.eltima.activator.xml file was not listed and remained. Connection restoration, cloud transfers, license deactivation and a Homebrew installation were not verified.