Updates to Full Disk Access in macOS
Apple announced upcoming macOS updates to tighten Full Disk Access controls, aiming to mitigate privacy risks posed by autonomous AI agents.
summary is enough The official post is a brief announcement, while the comment thread offers a lively debate on macOS security and AI agent sandboxing.
summary
Apple published a notice stating that Full Disk Access in macOS will receive stricter controls to curb risks from apps and autonomous AI agents accessing sensitive personal data. The current all-or-nothing permission model allows non-sandboxed tools to read everything from messages to browsing history. In the comment thread, developers debate whether this will improve security against prompt injections or merely add to macOS permission prompt fatigue. Many note that terminal emulators and AI tools currently bypass granular checks once granted broad permissions.
key points
- Apple highlights that Full Disk Access bypasses standard privacy controls, creating major risks as AI agents become more autonomous.
- Commenters debate whether terminal apps and shell environments complicate permission inheritance, making targeted file access difficult.
- Opinions are split: security-minded users welcome protection against rogue AI agents, while others fear escalating permission fatigue and heavy-handed platform restrictions.
who should read it
macOS developers and power users concerned about system security, privacy controls, and AI agent sandboxing.
discussion mixed
consensus
Participants generally agree that apps and AI tools shouldn't have unfettered access to systems, but many express frustration with macOS permission prompt UX.
pushback
Some argue that Full Disk Access is meant to give the owner total control, viewing Apple's tightening restrictions as paternalistic lockdowns.
If anything in a world with agents, these TCC dialogs just need to have an "allow once", just like Location Services has on iOS, and just like most harnesses have, a la "Do you want to allow $AGENT to run the following command?" A. Yes. B. Yes and don't ask for $command, C. No but instead just asking "Do you want to allow Claude Desktop access to files and folders on your Desktop?" A. Once. B. Always C. No
I think the issue comes in with terminal emulators and CLI harnesses. TCC permissions are inherited from the "responsible" process, so if you grant Terminal.app or ghostty.app FDA, you've …
It highlights the structural flaw where granting a terminal emulator Full Disk Access implicitly grants it to any shell command or script run inside it.
Generated by an LLM from the article and thread. Check the sources before relying on it.