How to uninstall RunCat Neo on Mac
Keep custom runner images and metric JSON files before removing RunCat Neo. Its publisher's listing supports PNG runner animations and user-provided metric files; those external files should remain wherever you stored them. This guide covers the Mac App Store app recorded as RunCatNeo.app, not a different RunCat edition.
Stop the menu-bar app
Quit RunCat Neo and verify its process has stopped in Activity Monitor. Copy wanted custom images, metric JSON and the existing sandbox container below to an independent backup, then verify the copies before clearing local settings. Move RunCatNeo.app from Applications to the Trash in Finder, and check System Settings › General › Login Items & Extensions if you enabled it at login.
Review recorded settings
The test identified ~/Library/Containers/com.kyome.Neo.RunCat and ~/Library/Application Scripts/com.kyome.Neo.RunCat. Open them with Finder's Go › Go to Folder after quitting. Keep the main container until settings you want are backed up, then remove only unwanted exact entries, preserving their parents and external custom assets.
Check the result
pgrep -ifl 'RunCatNeo|RunCat Neo'
ls -ld "$HOME/Library/Containers/com.kyome.Neo.RunCat"
No process match means no arguments matched these names; identify a surviving match before quitting it. A printed container remains, expected if retained. A missing-path error means that exact folder is absent, while permission or command errors leave its state unknown. Keeping custom PNG and JSON files is intentional.
What Mole lists
The main container, scripts folder and attributable temporary cache entries are selected by default. Back up or uncheck settings you want to keep; the optional app-data setting does not change these exact-main-app defaults. User-chosen custom files are not part of these named container rows.
What this test covered
RunCat Neo 1.0 was removed from the Mac App Store installation on September 21 and retested on September 26, 2026. The later run removed the app and selected original data paths. Custom runner restoration, user-defined metrics and sustained monitoring were not tested.
