How to uninstall LazyCat on Mac

LazyCat (懒猫微服, cloud.lazycat.client) is the desktop client for LazyCat private-cloud hardware, downloaded from lazycat.cloud. The files you keep on your LazyCat box live on the box, not on this Mac, so removing the client does not delete them. What can live on the Mac is a mount root, ~/lazycat_automount, which the client uses for network shares; it can hold the shared content of whatever is mounted there, so read the first step before you touch it. This guide covers the client 2.0.30 downloaded from that site and the Homebrew cask lazycat.

Quit the client and unmount shares

1. Quit 懒猫微服 from its menu bar or Dock icon. In the recorded test it ran 15 processes, including a bundled lzc-core helper, which Mole's Status page folded into one 懒猫微服 row. Search Activity Monitor for lzc and lazycat and check that nothing is left.
2. If you mounted shares from your box, disconnect or eject them first. Do not move ~/lazycat_automount while a share is mounted: the folder is the mount point, and moving it takes the mounted content with it.
3. Open System Settings › General › Login Items & Extensions. The client registers a login item that may show as LCMD; switch it off or let the uninstall below remove it.

Remove the app

Move 懒猫微服 from Applications to the Trash in Finder. LazyCat publishes no uninstall page that this guide could find, so the steps here come from the installed app and the cask.

Where the client keeps its data

In Finder, press Shift + Command + G and type the path. Skip any path that is not on your Mac.

The user cache root is where getconf DARWIN_USER_CACHE_DIR points. Those folders are rebuilt on the next launch.

Check the result

pgrep -il lzc
pgrep -il lazycat
ls -d "$HOME/Library/Preferences/cloud.lazycat.client.plist" "$HOME/Library/Application Support/lzc-client-desktop" "$HOME/Library/Logs/lzc-client-desktop" "$HOME/.config/lzc-client-desktop" "$HOME/lazycat_automount"
ls -d "$(getconf DARWIN_USER_CACHE_DIR)"cloud.lazycat.client*
mount | grep -i lazycat

• No output from pgrep means no process with that text in its name or arguments was found. A printed line means something is still running; identify it in Activity Monitor before quitting it.
• A path printed by ls still exists. No such file or directory applies to that path only.
• For the line with *, zsh, the default shell on macOS, prints no matches found when no temporary cache folder is left, which is the result you want. A printed folder is one that is still there.
• Any line from mount | grep -i lazycat means a share is still mounted. Eject it before touching ~/lazycat_automount.

If you installed it with Homebrew

brew uninstall --cask lazycat

The cask installs 懒猫微服.app and has no uninstall step of its own beyond removing the app. Its zap list is ~/lazycat, the preferences file, the recent-documents list cloud.lazycat.client.sfl* and the saved window state ~/Library/Saved Application State/cloud.lazycat.client.savedState. ~/lazycat sits outside ~/Library, so Mole never adds --zap for this cask and removes the rows you selected itself. Running brew uninstall --cask --zap lazycat yourself moves ~/lazycat to the Trash whatever you ticked in Mole, so open that folder first. The zap list does not name ~/Library/Application Support/lzc-client-desktop, ~/Library/Logs/lzc-client-desktop, ~/.config/lzc-client-desktop or ~/lazycat_automount.

Account

Removing the client does not remove your LazyCat account or unbind your box. Manage both on LazyCat's side.

What Mole lists

Mole selects the app, the preferences file, the recent-documents list and the two temporary cache folders when they are present. It removes the client's login item as part of the uninstall. It lists ~/Library/Application Support/lzc-client-desktop, ~/Library/Logs/lzc-client-desktop and ~/.config/lzc-client-desktop for review without selecting them, so tick them yourself after looking inside. If ~/lazycat exists, Mole lists it for review because the cask's zap list names it, and does not select it. It does not list ~/lazycat_automount, ~/Library/Application Support/lazycat or ~/.config/lazycat.

These defaults assume “Remove data and settings with apps” in General › Cleaning is off. With it on, Mole also ticks the three lzc-client-desktop rows, so open them before you turn it on. ~/lazycat stays unticked even then.

What this test covered

On October 19, 2026, the test removed a copy of LazyCat 2.0.30 for Apple silicon that was already installed on the test Mac. The client was not running, no share was mounted, and the test did not sign in or out of an account. With every listed row ticked, Mole moved the app and the four rows next to it to the Trash and then cleared the client's login item, which had shown as LCMD among the startup items before the removal. Three folders named after the client's package, lzc-client-desktop, stayed on disk because Mole did not list them in that pass; they were added to Mole as review rows afterwards, and that change was confirmed by a test in Mole's code rather than by a second removal. ~/lazycat_automount and the lzc-cli folders were left alone on purpose. Afterwards the app and its preferences were moved back from the Trash, which restored that install, and the client was launched to read Status: one 懒猫微服 row with 15 processes, lzc-core folded in. The client has no update feed that Mole reads, so Mole's update page showed no update channel. A Homebrew install was not tested.