How to uninstall Lody on Mac

Lody is a coding agent workspace from lody.ai that runs agents in parallel on the desktop, phone and browser, and gives each session its own Git worktree. Per its documentation, repositories it clones live in ~/.lody/repos, each with a shared bare repository, a cache and one worktree folder per session, and logs go to ~/.lody/logs. Unpushed branches and uncommitted work in those worktrees exist only on your Mac, so decide what to keep before you remove anything. Your conversation history and account live with Lody's service and stay there after the app is gone. This guide covers the Apple silicon disk image from Lody's update server and the Homebrew cask lody.

Quit and remove the app

1. Commit and push the branches you want from the worktrees under ~/.lody/repos, and copy out ignored files such as .env that you still need. Lody's worktree documentation says ignored files can be discarded when a worktree is cleaned up. Projects you added from your own folders live in those folders, not in ~/.lody, and removing a project in Lody does not delete the original folder.
2. If you also ran the Lody command line daemon on this Mac, stop it with lody daemon stop, which the CLI documentation describes.
3. Quit Lody with Command + Q. In the test the app and its helpers ran 8 processes, which Mole's Status page groups into one Lody row.
4. Open Finder, go to Applications and drag Lody to the Trash.

The test recorded no login item or launch agent for Lody.

Where the data lives

Press Shift + Command + G in Finder to open each path. Skip any path that is not on your Mac.

Check the result

pgrep -il lody
ls -d "$HOME/.lody" "$HOME/Library/Application Support/Lody" "$HOME/Library/Caches/ai.lody.desktop" "$HOME/Library/Preferences/ai.lody.desktop.plist"
launchctl list | grep -i lody

• No output from pgrep means neither Lody nor its helpers or the command line daemon are running. A printed line names a process still alive; quit it, or run lody daemon stop if it is the daemon.
• A path printed by ls still exists. A surviving ~/.lody is expected if you kept your repositories. No such file or directory means that path is gone.
• No output from launchctl means no Lody job is loaded for your user. A line means a background item is still registered; check Login Items & Extensions.

If you installed it with Homebrew

brew uninstall --cask lody

The cask has no uninstall step, so this removes the app and leaves your data. Its zap list covers ~/.lody, ~/Library/Application Support/Lody, the cache, HTTPStorages and preferences entries above, ~/Library/Preferences/lody-desktop-nodejs and the recent-documents list. Running brew uninstall --cask --zap lody therefore deletes your repositories and worktrees with everything else, and it does not read Mole's checkboxes. Mole adds --zap only when its whole removal scope passes its zap gate; ~/.lody is outside ~/Library, so Mole never runs this cask's zap and removes the rows you selected itself.

Account and subscription

Uninstalling does not sign you out on Lody's side, delete your sessions, cancel a plan or delete your account. Lody's session documentation says a session can be permanently deleted from the archive list, which removes its conversation history and cannot be undone. If you authorized Lody on GitHub, its GitHub guide points to github.com/settings/installations for removing the Lody GitHub App.

What Mole lists

Mole selects the app, the preferences file, the cache, HTTPStorages, the six web cache folders inside Application Support/Lody and both temporary cache folders. It lists ~/Library/Application Support/Lody, ~/Library/Preferences/lody-desktop-nodejs and ~/.lody for review and selects them by default, so untick ~/.lody if you still need unpushed work in it. Before removing, Mole asks Lody to quit. The recent-documents list is only found when Mole can read that folder, which needs Full Disk Access.

What this test covered

On November 9, 2026, the test downloaded the Apple silicon disk image 0.110.1 from Lody's update server, whose sha256 matched the Homebrew cask, copied the app to Applications without running brew install, opened it once and quit it. It was removed with a source-built, re-signed Debug build of Mole with every review row ticked; Mole's notarized release build was not used. Mole moved 14 rows and the app to the Trash with no failures. The only item left was the recent-documents file, because that build ran without Full Disk Access and could not read its folder. Status showed one Lody row with 8 processes, and Mole detected an Electron updater; no update was run. No account was signed in, so repository cloning, sessions, worktrees, the command line daemon, the mobile app and a Homebrew-managed uninstall were not tested.