How to uninstall LobeHub on Mac

LobeHub 2.x keeps your agents and conversations in your account, on LobeHub Cloud or on the server you host yourself, so removing the Mac app does not delete them. What stays on the Mac is ~/Library/Application Support/LobeHub, plus, if you used the 1.x desktop app, a local database from that version. Export anything you want from it before you remove it. These steps cover LobeHub downloaded from its GitHub releases and the Homebrew cask lobehub.

Check for an old local database first

LobeHub's migration guide explains that 1.x Desktop offered a local database mode, that 2.x removed it, and that upgrading does not delete the old database files. If you ever used 1.x in local mode, those files may be the only copy of those conversations. The guide gives the macOS location as ~/Library/Application Support/lobehub-storage/lobehub-local-db; the desktop app's source code puts its storage folder inside LobeHub's own folder, ~/Library/Application Support/LobeHub/lobehub-storage, so check both.

To keep that history, follow the guide: install a 1.x build, export with Settings › Data Storage › Export Data, and import the file into 2.x with Settings › Data Storage › Import Data. Keep the old files until the import works.

Quit LobeHub and remove the app

  1. Quit LobeHub from its application menu.
  2. Search Activity Monitor for LobeHub and check that the app and its helper processes have exited.
  3. Move LobeHub from the Applications folder to the Trash.

Removing the app does not sign you out on other devices, delete your LobeHub Cloud data or cancel a subscription. Manage those in your account.

Where LobeHub keeps its data

Location What it holds What to do
~/Library/Application Support/LobeHub The desktop app's local state; its lobehub-storage folder holds locally stored files and installed plugins Remove it once you no longer use LobeHub on this Mac and have checked for 1.x data
~/Library/Application Support/lobehub-storage The 1.x local database location named in LobeHub's guide Keep it until you have exported what you need
~/Library/Logs/LobeHub App logs Safe to remove after quitting
~/Library/Preferences/com.lobehub.lobehub-desktop.plist App preferences Safe to remove for a clean reinstall

The contents of lobehub-storage come from LobeHub's desktop source code; the other paths come from the Homebrew cask and this test.

Check the result

Run these read-only commands in Terminal:

pgrep -lf LobeHub.app
ls -d "$HOME/Library/Application Support/LobeHub" "$HOME/Library/Application Support/lobehub-storage"
  • No output from pgrep means no process is running from LobeHub.app. A listed process means the app or a helper is still open.
  • ls -d prints each folder that still exists and reports "No such file or directory" for the rest. A surviving folder is expected if you kept it; a missing lobehub-storage usually just means you never used 1.x local mode.

If you installed it with Homebrew

Mole skips --zap when its list reaches unchecked or shared data, or cannot be fully checked, and still cleans the leftovers you selected.

The lobehub cask's zap list includes ~/Library/Application Support/LobeHub, with any 1.x data stored inside it, plus logs, preferences, saved window state and the recent-documents list. It also lists ~/Library/Application Support/LobeHub-Beta, the matching beta logs and the beta preferences file, which belong to LobeHub's beta build; if you use that build too, a zap removes its data as well. Running brew uninstall --cask --zap lobehub yourself moves all of these to the Trash, whatever you ticked in Mole. To keep them, remove only the app:

brew uninstall --cask lobehub

What Mole lists

This is how Mole handles LobeHub installed from the official download:

  • ~/Library/Application Support/LobeHub is listed but not selected. The rebuildable caches inside it, Cache, Code Cache, GPUCache, DawnGraphiteCache, DawnWebGPUCache and blob_storage, are separate rows selected by default.
  • ~/Library/Logs/LobeHub, the preferences file, the app's recent-documents list and its temporary cache folders are selected by default.
  • No 1.x local database or LobeHub-Beta folder existed in the test, so this guide makes no claim about how those are listed; check them with the commands above.

What this test covered

On September 26, 2026, LobeHub 2.2.18 was installed from the official package Homebrew's cask points to, checked against its checksum and copied into Applications, launched once without signing in, and uninstalled with a development build of Mole with every listed row ticked, including the ones Mole leaves unchecked. Mole's Status page showed LobeHub as one row with six processes. The app, the 13 MB support folder and its caches, the logs and the preferences, 13 items in all, went to the Trash, and none of them was still on disk afterwards. No login item or launch agent appeared. No account, cloud data or 1.x local database was involved, and the Homebrew cask was not uninstalled. An earlier test on September 21, 2026 removed LobeHub 2.2.17, its support folder, its logs and a lobehub-storage folder.