How to uninstall OpenLogi on Mac

OpenLogi is an open-source replacement for Logitech Options+ that remaps buttons on Logitech HID++ devices, from openlogi.org and its GitHub project. Your button bindings are a plain TOML file you own; the site says the app writes straight to config.toml, and the test found an openlogi folder in ~/.config. Copy that file first if you want to keep your bindings. OpenLogi also runs a background agent and an overlay helper that start from inside the app, so quit it properly before you trash it. This guide covers the disk image from openlogi.org and the Homebrew cask openlogi.

Quit and remove the app

1. Copy the ~/.config/openlogi folder somewhere safe if you want your bindings; the site names the file config.toml, and the test saw the folder but did not open it.
2. Quit OpenLogi with Command + Q, then check that its background agent is gone with the commands below. In the test the first launch registered a background job labeled org.openlogi.agent.service and 5 processes, including openlogi-agent and openlogi-overlay, both bundled inside the app as login items; Mole stopped the job during the uninstall and it was gone afterwards. You can also look under System Settings › General › Login Items & Extensions for OpenLogi entries and turn them off.
3. Open Finder, go to Applications and drag OpenLogi.app to the Trash.
4. If you gave OpenLogi permissions such as Accessibility or Input Monitoring, remove its entries in System Settings › Privacy & Security. The test never opened those settings, so which permissions it asks for was not checked.

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 openlogi
launchctl list | grep -i openlogi
ls -d /Applications/OpenLogi.app ~/.config/openlogi ~/.local/share/openlogi ~/Library/Preferences/org.openlogi.*.plist

• No output from pgrep means OpenLogi, its agent and its overlay are not running. A printed line is a process still alive; quit it and run the command again.
• No output from launchctl means no OpenLogi job is loaded. A line with org.openlogi.agent.service means the background job is still registered; log out and back in, or restart the Mac, once the app is gone.
• For ls -d, "No such file or directory" means that path is gone. A printed path is still on disk; a surviving ~/.config/openlogi is expected if you kept your bindings.

If you installed it with Homebrew

brew uninstall --cask openlogi

The cask does more than remove the app on an ordinary uninstall: it unloads org.openlogi.agent.service, quits the three OpenLogi bundles and removes the openlogi command line link it adds. brew uninstall --cask --zap openlogi also trashes ~/.config/openlogi, ~/.local/share/openlogi, ~/Library/Caches/org.openlogi.openlogi, both preferences files and the saved window state, which deletes your bindings. A direct brew command does not read Mole's checkboxes. The zap list reaches outside ~/Library through the two dot folders, so Mole leaves --zap off for this cask and removes the rows you selected itself. The Homebrew install was not tested.

What Mole lists

Mole selects the app, org.openlogi.openlogi.plist and its two temporary cache rows. It lists org.openlogi.overlay.plist for review and selects it by default, and lists ~/.config/openlogi and ~/.local/share/openlogi for review without selecting them, so tick them yourself once your bindings are backed up. Before removing, Mole stops the org.openlogi.agent.service background job and asks OpenLogi to quit.

What this test covered

On November 9, 2026, the test downloaded OpenLogi 0.9.0 for Apple silicon as a disk image from openlogi.org, whose checksum matched the Homebrew cask, copied the app to Applications without running brew install, launched it once and quit it. The first launch registered the org.openlogi.agent.service background job. A source-built Mole with the review rows ticked stopped that job, moved the app and 6 rows to the Trash and left the name rescan empty; the job was no longer listed afterwards. Status showed one OpenLogi row with 5 processes. Mole detected a Sparkle updater, and no update was run. No Logitech device was paired or remapped, so the bindings, permissions and the command line link were not tested, nor were the Homebrew install and Mole's notarized release build.