How to uninstall LobeHub on Windows

LobeHub 2.x keeps your agents and conversations in your account, on LobeHub Cloud or on the server you host yourself, so removing the desktop app does not delete them. What stays on this PC is the app's own folder in %APPDATA%\LobeHub, plus, if you ever used the 1.x desktop app in local database mode, the data from that version. This guide covers LobeHub installed per-user from the LobeHub.LobeHub winget package.

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 used that mode, those files may be the only copy of those conversations. Follow the guide to export them from a 1.x build and import them into 2.x, and keep %APPDATA%\LobeHub until the import works. This test used 2.x only, so it did not see where 1.x kept its database on Windows.

Quit LobeHub first

Quit LobeHub from its window menu. It runs as several LobeHub.exe processes, so check Task Manager (Ctrl+Shift+Esc) for any still listed before you uninstall. The test found no startup entry.

Remove the app with its own uninstaller

Go to Settings › Apps › Installed apps, find LobeHub, and choose Uninstall, or run:

winget uninstall --id LobeHub.LobeHub

Where the data lives

Check the result

Run these read-only commands after the uninstall finishes:

Get-Process LobeHub -ErrorAction SilentlyContinue
winget list --id LobeHub.LobeHub
Test-Path "$env:LOCALAPPDATA\Programs\LobeHub"
Test-Path "$env:APPDATA\LobeHub"
Test-Path "HKCU:\Software\Classes\lobehub"

• No output from Get-Process only means this query observed no matching process; a suppressed error leaves the running state unknown. A listed process means a window or helper is still open.
• A completed winget list query with no match means the package record is gone; a matching row means the uninstall did not finish.
• The first Test-Path returning False means the program folder is gone; True means files remain there.
• Test-Path "$env:APPDATA\LobeHub" returning True means the app's local state is still there, which is expected unless you removed it yourself.
• The last Test-Path returning True means the lobehub:// link registration is still there and points at a program that no longer exists; False means it is gone.

If you installed it with winget

winget uninstall runs the same uninstaller Settings › Apps uses and removes the same program files; it does not touch %APPDATA%\LobeHub on its own.

Account and subscription

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

What Mole lists

For LobeHub installed per-user from winget:

• The program folder goes with the app row.
• %LOCALAPPDATA%\lobehub-desktop-updater, which holds only downloaded update installers, is selected by default.
• %APPDATA%\LobeHub is listed but not selected. The rebuildable caches inside it, Cache, Code Cache, DawnGraphiteCache, DawnWebGPUCache, GPUCache and logs, are separate rows selected by default.
• The Desktop and Start Menu shortcuts are selected by default.
• The lobehub:// link registration, the app's notification registration and a row grouping Windows' own records of when you opened the program are selected by default; the registrations are backed up to a .reg file before removal.

What this test covered

Tested on September 29, 2026 with LobeHub 2.2.18 installed through winget, per-user scope, from an elevated session; a normal per-user install needs no administrator access. The uninstaller is NSIS and ran silently. The app was opened once without signing in. Every listed row was ticked and removed in this test. Not verified: a signed-in account, cloud sync, and 1.x local database data.