Turn off Apple Intelligence on macOS 27 and get its disk space back
A new open-source script that removes Apple’s on-device AI models from macOS 27 is drawing interest from users frustrated that “Apple Intelligence” quietly consumes 10–30 GB of non‑removable storage. Commenters debate whether running such tools via `curl | bash` is safe, but many see them as necessary “debloat” workarounds on machines that ship with small, non‑upgradeable SSDs. The broader conversation centers on user control, opaque opt-out mechanisms for AI features, and a perceived shift of macOS toward Windows-style bloat and enshittification.
Apple Intelligence disk usage and bloat
- Many complain that Apple Intelligence models consume 8–30+ GB, which is significant on 256 GB (or smaller education 128 GB) Macs and tight iOS devices.
- Users object that these models are downloaded automatically with no simple, official way to reclaim the space, even if the AI features are never used.
- Some argue 10–12 GB is modest for local models and worth it for on-device AI, but others point out macOS already has a large footprint and cumulative “feature creep” is painful.
Control, consent, and user hostility
- Strong sentiment that OS features consuming large resources should be clearly opt‑in or at least easily removable via a first‑class setting.
- Several users report that disabling Siri/AI now requires multiple hidden toggles (Screen Time, per‑app settings), is confusing, and may not reliably remove models.
- Some see this as part of a broader pattern: Apple deciding what runs on “your” hardware and removing options that existed in prior OS versions.
curl | bash installer controversy (for this tool and in general)
- Large subthread debates the security of
curl | bashinstallation for the debloating tool. - Critics stress it normalizes pasting arbitrary commands, allows server‑side targeting, and makes auditing harder than downloading a fixed artifact.
- Defenders argue people already run tons of unaudited code (apps, installers, npm/pip), that TLS and signatures mitigate much of the risk, and that you can inspect or tee the script.
- Some suggest feeding scripts into LLMs for quick audits, though others doubt this is reliable.
Comparisons to Windows, Linux, and “enshittification”
- Multiple users liken this to Windows debloat scripts and OEM crapware, saying macOS now also needs third‑party tools to strip unwanted features.
- Others argue Apple’s “bloat” is at least first‑party functionality (unlike random trialware), but pushback notes it’s still forced and space‑hungry.
- Several report moving or planning to move to Linux (often KDE or GNOME) for more control and less lock‑in, while acknowledging Linux’s own rough edges.
Backwards compatibility, Rosetta, and OS updates
- Some see the removal/retirement of Rosetta 2 and forced feature bundles as signs macOS is becoming something users must “maintain” like Windows.
- Others counter that staying near the latest macOS is important for ecosystem compatibility and that legacy emulation can’t be kept forever.
General AI and OS fatigue
- Many express broad AI fatigue: AI being pushed into every product (OS, browser, tools) regardless of user need.
- Desire for “black edition” or “server” macOS variants without AI, screensavers, and other heavy consumer features appears repeatedly.