Apple AI ejector

That list matters because "turn off AI" no longer names one action. You may want silence, less server use, no local inference, recovered storage, or a policy that survives an update. Those outcomes need different checks.

Apple says macOS 27 can use up to 14 GB for Apple Intelligence on newer eligible Macs and up to 8 GB on other supported Macs. Apple's user guide explains how to turn individual features off. It does not present those switches as a model-removal control.

What RemoveMacAI actually does

RemoveMacAI builds a removable configuration profile. The profile forces Apple Intelligence preferences off and redirects selected model downloads to a closed local port. The tool then asks Apple's asset service to remove known model sets. It does not disable System Integrity Protection or delete files under /System itself.

The source also keeps feature selection and model deletion linked. If you choose to keep Writing Tools, for example, the tool keeps the foundation models that Writing Tools needs. Its catalog currently covers Siri, Writing Tools, Genmoji, Image Playground, summaries, Photos tools, inline predictions, ChatGPT integration, and Xcode predictive completion.

Artifact check before opinion

Release 0.2.3 has a versioned Apple-silicon archive and a separate checksum file. The archive matched the published SHA-256 value d9987c…3718. GitHub's attestation API lists one provenance record for that digest. The tarball contains the binary, license, and third-party notices.

That is better than treating the moving main branch as the artifact. It still does not prove the tool behaves correctly on your Mac. Download the pinned release, verify its digest, run its dry-run mode, inspect the generated profile, then decide. The one-line installer performs a checksum check, but piping a live script into a shell gives you less stable evidence than saving a named release first.

RemoveMacAI is interesting because it treats absence as a maintained state. The profile does not only switch current features off. It also tries to stop the same assets from quietly returning. That is the right shape for any opt-out that claims to persist.

The tool is also young and uses macOS internals that can move. Its own README limits support to Apple silicon and macOS 27.0 or 27.0.1 with the current release. Pinning the version and checking again after an OS update are part of the job.

The better operating rule is simple. Start with Apple's switches when the problem is distraction. Move to model removal only when disk use or a local-model boundary justifies the extra mechanism. A capability should have an entry path, an exit path, and a receipt for both.