How to uninstall Stability Matrix on Mac

Keep models, images, workflows and package-local files before removing Stability Matrix. Its official repository separates the portable Data Directory and shared model library from the launcher. Removing the app is not a request to delete all generated work or every installed Python environment.

Stop packages before removing the launcher

Let wanted generations finish, then use Stop on each running package's card in Packages, as the package guide describes. Closing a browser tab does not stop the backend.

Locate the Data Directory you use and independently copy wanted models, outputs, .smproj projects, workflows and configuration outside every sync root and removal folder. Package-local files need their own check even if shared models are kept. Verify the copies before deleting anything.

If you also want to remove an installed package, keep Stability Matrix available: open that package's three-dot menu, choose Uninstall, review the warning and confirm the displayed package name. That operation removes the installation folder, Python environment, extensions and custom files inside it. Shared models outside it remain, but package-local models and outputs can be lost. Do not delete models in Checkpoint Manager merely to uninstall the launcher.

After finishing optional package removal, quit Stability Matrix and move Stability Matrix.app from Applications to the Trash in Finder.

Review the cask data folder

The current cask names ~/Library/Application Support/StabilityMatrix. Open it through Finder's Go › Go to Folder, copy wanted contents before clearing it, and keep any user-selected Data Directory or shared library whose use you have not resolved. The cask path is not proof that every model or package lives there.

If you installed it with Homebrew

The cask declares no separate ordinary uninstall step beyond its managed launcher.

brew uninstall --cask stability-matrix

Zap removes the support folder above. A direct brew uninstall --cask --zap stability-matrix ignores Mole's checkboxes. Mole uses zap only when its whole scope passes selection, ownership and safety checks; selected remnants otherwise use its own Trash flow. Back up and uncheck any data you still need.

Check the result

pgrep -ifl 'Stability Matrix.app'
ls -ld "$HOME/Library/Application Support/StabilityMatrix"

No process match means no arguments matched the launcher path; it does not prove every external Python backend stopped. Verify those separately through Packages and their executable paths before data removal. A printed support folder remains, expected if retained; a missing-path error means that exact folder is absent. Other errors leave the result unknown, and preserved models are an intended result.

What Mole lists

The display-name/cask support folder is reviewed app data, unchecked with Remove data and settings with apps off. Turning it on can preselect eligible unshared data, so keep wanted setup unchecked. Mole's app rows do not decide which shared models, independent packages or generated projects you still need.

What this test covered

On September 22, 2026, the official DMG's Stability Matrix 2.16.4 app was copied into Applications and removed with its selected small support folder. The run did not create a shared model directory. Package installation/uninstallation, model generation, populated Data Directory recovery and the Homebrew route were not tested.