How to uninstall Sensei on Mac

Sensei is Cindori's Mac maintenance and monitoring app, with a menu bar monitor called Sensei Monitor. What it keeps in your home folder is settings, caches and a small Application Support folder; none of it is personal data. What you may want to keep is the license: Cindori's License Manager is where you deactivate a Mac or move the license to another one, so do that before you remove the app. Some Sensei features install a privileged helper and system services after asking for an administrator password; the test below never turned them on, and the paths for them come from the Homebrew cask. This guide covers the disk image from cindori.com and the Homebrew cask sensei.

Quit Sensei and Sensei Monitor

1. Quit Sensei with Command + Q.
2. If Sensei Monitor is in the menu bar, quit it from its menu. It is registered as a background item from inside the app, under the label org.cindori.SenseiMonitor.agent; you can also turn Sensei off in System Settings › General › Login Items & Extensions.
3. Open Activity Monitor and search for Sensei. Nothing should be left.

Move the app to the Trash

1. Move Sensei.app from Applications to the Trash, as described in Apple's Delete or uninstall apps on Mac.
2. In Finder, press Shift + Command + G, open each path below and move what you no longer need to the Trash. Moving a file out of /Library asks for an administrator password.

Where Sensei keeps its files

Check the result

pgrep -il sensei
launchctl list | grep -i cindori
ls -d /Applications/Sensei.app ~/Library/Application\ Support/Sensei /Library/PrivilegedHelperTools/org.cindori.SenseiTool /Library/LaunchDaemons/org.cindori.Sensei*

• No output from pgrep means neither Sensei nor Sensei Monitor is running. A printed line names a process that is still alive; quit it, or restart the Mac once.
• No output from launchctl means no Sensei job is loaded for your user. A line with org.cindori.SenseiMonitor.agent means the monitor is still registered; turn it off in Login Items & Extensions, or log out and back in after the app is gone. System services do not show up here; the ls -d line covers them.
• For ls -d, "No such file or directory" means that path is gone. A printed path is still on disk.

If you installed it with Homebrew

brew uninstall --cask sensei

The cask does more than remove the app on an ordinary uninstall: it quits Sensei and Sensei Monitor, unloads org.cindori.SenseiMonitor, org.cindori.SenseiMonitor.agent and org.cindori.SenseiTool, and deletes the helper and the three service files from /Library, so Homebrew may ask for your password. brew uninstall --cask --zap sensei also deletes its zap list, which includes Sensei's crash reports in /Library/Logs/DiagnosticReports and the folders in ~/Library above; it does not read Mole's checkboxes. Mole adds --zap only when every zap path is inside ~/Library and matches rows you reviewed. Sensei's list reaches outside ~/Library, so Mole leaves --zap off and removes the rows you selected itself. The Homebrew install was not tested.

What Mole lists

Mole selects the app, ~/Library/Application Support/Sensei, both caches, both web storage folders, the cookie file, Sensei's preferences and its temporary caches. Sensei Monitor's preferences file and ~/Library/Caches/amplitude/org.cindori.Sensei are listed for review. Before removing, Mole asks Sensei to quit and unloads the monitor's background item. Mole does not list ~/Library/Caches/amplitude/org.cindori.SenseiMonitor, which was an empty folder in the test. Status shows Sensei as one row, and the update page reads Cindori's own Sparkle feed.

What this test covered

On October 31, 2026, Sensei 2.1.3 was installed from Cindori's disk image on a test Mac and removed with a source-built Mole. Mole moved the app and 11 rows to the Trash. Before the uninstall the monitor's background item was registered but not running; afterwards it was not loaded. Sensei Monitor's empty analytics folder remained and was then removed by hand. No license was activated, no feature that installs the privileged helper or system services was turned on, so their removal was not tested, and the Homebrew cask was not tested.