v1.0.5

What's Changed

• Fixed the package's Mole pre-install. The postinstall script fetched Mole's installer from mole.fit/install.sh, which returns 404, so Mole was never pre-staged. It now uses the same GitHub URL as the in-app installer and writes its log to /Library/Logs/MacMoleManager-mole-install.log (it previously went to /tmp, which is cleared on reboot). Mole's installer needs admin access to write /usr/local/bin, so on a standard-user Mac the pre-install is still expected to fall through to the in-app "Install Mole" flow with Privileges.
• One-click repair for a broken Mole install. If mole is present but the support files it loads from ~/.config/mole are missing (deleted by hand, removed by a cleanup tool, or never created for that user), the app previously showed a raw shell error with no way forward. It now explains the problem and offers a "Reinstall Mole" button, including when the error comes from "Check for Mole Updates". The Homebrew repair button now works from that path too.
• PPPC template: pre-approve System Events. Mole triggers a "MacMoleManager wants to control System Events" prompt during Clean, and the template only covered Finder. Packaging/PPPC-template.mobileconfig now grants both.
• PPPC template: removed the deprecated Allowed key. Each entry carried both Allowed and Authorization, and macOS rejects a payload with both ("the key 'Authorization and Allowed' is not allowed"). Only Authorization remains.
• Packaging docs. The PPPC template and Packaging/README.md now note that Mosyle's Security & Privacy form keeps only one Apple Events receiver per app, so this profile should be uploaded under Certificates / Custom Profiles.

Full Changelog: v1.0.4...v1.0.5

v1.0.4

What's Changed

• Fixed Mole failing to install after a .pkg/Self Service deployment. The package's postinstall script ran Mole's installer and launched MacMoleManager as the logged-in user, but with root's HOME (/var/root) still in the environment. Mole's installer couldn't write ~/.config or read ~/.bash_profile, so it wasn't pre-installed, and the in-app "Set Up Mole" flow then failed the same way with Permission denied. The postinstall now sets HOME, USER, and LOGNAME explicitly for the console user.
• MacMoleManager now corrects a bad inherited HOME at launch. If an installer, MDM script, or other tool starts the app with the wrong home directory, the app resets it from the user's account record so Mole, its installer, and Homebrew all write to the right place.

Full Changelog: v1.0.3...v1.0.4

v1.0.3

What's Changed

• Self-heal a broken Homebrew install of Mole. If Mole's own wrapper script fails because its Homebrew Cellar files are missing — e.g. after an interrupted brew upgrade or a Migration Assistant transfer that didn't carry over Homebrew's internal symlinks — MacMoleManager now recognizes that failure and offers a one-click "Reinstall via Homebrew" fix instead of a raw shell error. If Homebrew's own reinstall then fails to relink (a separate, common Homebrew failure), it automatically retries with brew link --overwrite before giving up. If Homebrew still can't recover, a second button, "Install Mole Directly," bypasses Homebrew entirely using Mole's own installer — no need to uninstall anything first.
• Added an automated release pipeline. Pushing a version tag now builds, signs, notarizes, staples, and publishes a GitHub release automatically via GitHub Actions — both a .zip (direct download) and a fleet-deployable .pkg (Mole pre-staged via postinstall). This release is the first one built and published through it.

Full Changelog: v1.0.2...v1.0.3

v1.0.2

v1.0.2 — Admin access, first-run setup, and a distributable PKG

Added

Guided first-run setup If Mole isn't installed yet, MacMoleManager now walks you through it instead of just showing an error banner — what Mole is, what the installer is about to do, and when it might ask for admin access. Reopen it any time from the "What Is This?" link on the missing-Mole banner.
Privileges integration for admin access If your account doesn't have admin rights, MacMoleManager no longer just surfaces a raw sudo error — it now offers to request temporary admin rights directly through Privileges (if installed) and automatically retries the install/update once granted. Without Privileges, it points you at Users & Groups instead.
A friendlier prompt before Finder access Revealing a file in Finder now explains, once, that macOS is about to ask permission for MacMoleManager to control Finder — instead of that system dialog appearing out of nowhere.
A distributable, fleet-ready .pkg New Packaging/ directory with a build-pkg.sh script (archives/signs/notarizes via Xcode's Direct Distribution flow, then builds and notarizes the installer package) and a postinstall script that pre-installs Mole and opens Full Disk Access settings on unmanaged Macs.
A PPPC profile template for managed fleets Packaging/PPPC-template.mobileconfig pre-authorizes Full Disk Access and Finder automation for MacMoleManager's bundle ID — push it via Mosyle (or any MDM) and your users skip both permission prompts entirely.

Fixed

Corrected the About panel's MoleUI credit, which was misattributed to tw93 — it's Zhili1004's project — and added the missing link.

Notes for other Mac admins

If you're deploying this on a managed fleet: the Packaging/README.md walks through building the signed/notarized .pkg and deploying the PPPC profile so your users never see the Full Disk Access or Finder-automation prompts at all. On an unmanaged/personal Mac, the in-app onboarding and priming dialogs handle both instead — no profile required.

Installation

Managed fleet: deploy MacMoleManager-1.0.2.pkg via your MDM (see Packaging/README.md).
Personal Mac: download the .pkg, double-click to install, or grab the .app directly if you'd rather skip the installer.

v1.0.1

Add elevated-install fallback for fresh Macs needing sudo

On a Mac with no prior Homebrew/CLT install, install.sh needs sudo and its lock-reauthentication step touches /dev/tty directly, which fails under a plain Process/Pipe child. installMole() now falls back to a real-pty elevated install when the promptless path fails.

Full Changelog: v1.0.0...v1.0.1

v1.0.0

v1.0.0 -- Initial Release

MacMoleManager

A native macOS app that wraps Mole — the open-source mole CLI for cleaning, uninstalling, analyzing, and monitoring a Mac — in a SwiftUI interface. Built for admins who want Mole's functionality without dropping to Terminal, and originally developed to replace a swiftDialog-based shell script for exactly that purpose.

Requirements

• macOS 14.0 (Sonoma) or later
• Full Disk Access granted to MacMoleManager (System Settings → Privacy & Security → Full Disk Access) for complete scan results.

Installation

Download MacMoleManager.zip, unzip, and drag the app to your Applications folder.

Built on mole by tw93 and contributors, as well as inspired by MoleUI by Zhili1004.