Uninstall Another Redis Desktop Manager on Mac
Record the Redis connection details you will need again, including SSH settings, before removing Another Redis Desktop Manager. The databases live on their servers. The September 19, 2026 record covers the app copied from the official package.
Quit and remove the app
Disconnect from Redis, quit the desktop app and move it to Trash. Keep SSH private keys and server databases out of this uninstall. The official page has more product information.
Review the app’s data
The cask lists ~/Library/Application Support/another-redis-desktop-manager and exact me.qii404.another-redis-desktop-manager preferences. The support folder may contain saved connections; inspect it before removal.
If you installed it with Homebrew
The Homebrew cask has its own --zap list. brew uninstall --cask another-redis-desktop-manager removes the cask without that list; brew uninstall --cask --zap another-redis-desktop-manager also acts on its listed data without consulting Mole’s checkboxes. Zap includes saved local connection state, so preserve it if needed. Mole also suppresses zap if its list would cross an unchecked, shared, unknown, or unsupported path; selected remnants still follow Mole’s own deletion path.
brew uninstall --cask another-redis-desktop-manager
Check the result
These commands inspect the running process and one relevant location. They do not remove anything:
pgrep -il "Another Redis Desktop Manager"
ls -ld "$HOME/Library/Application Support/another-redis-desktop-manager"
No pgrep match means no process with that name is running; a match needs identification before quitting anything. A listed path still exists, while an ls “No such file” error means only that exact path is absent. A permission error is inconclusive.
What Mole lists
Mole lists the display-name Application Support folder for review, unchecked. Exact bundle-ID preferences can be selected by default; it does not delete remote Redis data or SSH key files.
What this test covered
The September 19, 2026 official-package test of version 1.7.4 left the display-name support folder unchecked. It did not verify restoration of saved connections or any remote Redis changes.
