On 2 October 2026 Apple told developers it will add controls so Full Disk Access — the Mac privacy switch that lets one app read protected private data across the disk — can be turned on only with very explicit user action. The reason they named is AI agents: programs that loop, call tools, and keep going. They did not name a ship date, a macOS version, or the new dialog. The switch in System Settings tonight is still the live one.

Checked on 23 October 2026 against Apple’s developer note “Updates to Full Disk Access in macOS” (2 October 2026), OpenAI’s dots help pages, Meta’s public statements on Muse, and Apple DTS posts on the Developer Forums about which app TCC treats as responsible. Related posts on this site: OpenAI dots, Claude Code sandbox, and coop sandbox.
What Apple actually published

Apple’s note is two short paragraphs. The load-bearing lines, in their framing:
- Full Disk Access “largely sidesteps” the controls that protect private data.
- It exists “to allow backup apps to function properly.”
- Some developers use it in ways that can expose “files, mail, messages, and even browsing history” without the user fully understanding that exposure. Communication apps can also expose the other person in the thread.
- Going forward, additional controls will require “very explicit user action” for this “extraordinary level of access.”
- “As AI agents become increasingly capable and autonomous, the risks associated with this level of access will grow substantially.”
That is the whole announcement. No API diff. No screenshot. No calendar.
| Fact | Detail |
|---|---|
| Date | 2 October 2026 |
| Venue | Apple Developer News |
| Named products | None (no Muse, dots, or ChatGPT in Apple’s text) |
| Ship date | Not given |
| Live control today | System Settings → Privacy & Security → Full Disk Access |
The week that sat in front of the note

Keep three threads separate. Mixing them turns a class-level warning into a false accusation.
| Date | Event | What it is not |
|---|---|---|
| 29 Sep 2026 | OpenAI shipped dots (cloud computers for agents) | Not a macOS Full Disk Access grant |
| Late Sep 2026 | Inc. columnist Jason Aten says Muse knew his Messages content; Meta disputes it (TechCrunch, 30 Sep) | Not settled by Apple’s note |
| 2 Oct 2026 | Apple’s FDA note | Not a ruling on Muse or dots |
OpenAI’s default for a dot is work on its own cloud computer. OpenAI’s help centre says access to your local computer is optional and starts turned off; you connect it from the ChatGPT desktop app and can revoke it. Meta’s public line on Muse: Messages content needs Full Disk Access and a Messages connector, both opt-in. Apple named neither product. It named the class: agents, plus developers who already hand out the master key quietly.
Four gates, one master key

A file on a Mac is bytes at a path. Reading it is a system call. Several gates can say no:
- Unix permissions — owner/group/everyone bits. They do not know that a folder is Mail.
- App Sandbox — App Store apps live in a container plus files you pick. Many agent tools are not sandboxed Mac App Store apps.
- TCC (Transparency, Consent, and Control) — the subsystem behind Privacy & Security. It covers camera, mic, contacts, and folders Apple treats as sensitive. It applies even to root.
- Full Disk Access — one TCC service (internal name
kTCCServiceSystemPolicyAllFiles). System-wide for the app you toggle. Not a per-file yes.
| What an agent might want | Where it tends to live |
|---|---|
| ~/Library/Mail | |
| Messages | ~/Library/Messages |
| Safari data | ~/Library/Safari |
| Cookies | ~/Library/Cookies |
| The permission database itself | ~/Library/Application Support/com.apple.TCC/TCC.db |
Apple’s note calls out files, mail, messages, and browsing history on purpose. A backup tool needs a coarse hole because a backup that skips Mail is not a backup. An agent “helping in the repo” does not.
Why Terminal’s grant is the one that bites

Apple’s DTS guidance: if you run a tool from Terminal, the responsible code for TCC is Terminal, not a binary named claude or codex. Grant Full Disk Access to Terminal for a one-off backup, and every coding agent you later launch from that Terminal inherits that responsible-app check when it touches a protected path.
Claude Code’s /sandbox is a different lock. On macOS it uses Seatbelt around the agent’s shell commands. It can limit writes and network. It does not flip the Full Disk Access row off in Settings. Two locks. Turning the inner one on does not relock the outer one.
| Computer | Who holds the TCC identity | Default disk risk |
|---|---|---|
| Your terminal (Claude Code, Codex CLI) | Terminal / iTerm / Warp / Ghostty | High if FDA is on for that terminal |
| Desktop agent app (e.g. Muse) | The app itself | Only what you toggled for that app |
| Cloud agent (OpenAI dot) | Their VM, until you connect the laptop | Local disk out by default |
Audit the switch you have tonight
Apple has not replaced the control yet. Two minutes:
- Open System Settings → Privacy & Security → Full Disk Access.
- Look for Terminal, iTerm, Warp, Ghostty, Claude, Codex, ChatGPT, Muse, and backup tools you do not recognize.
- If a terminal app is on, assume every agent started there can attempt the protected set.
- Turn FDA off unless that app’s real job is a full backup or mail archive. A git repo does not need ~/Library/Messages.
- For Muse-style apps, also clear any Messages connector if you do not want messages in the loop.
- For a dot, leave the laptop disconnected unless a task truly needs local files. Disconnect when done.
For a coding agent, the decision rule is short:
If you manage Macs with MDM, use a Privacy Preferences Policy Control (PPPC) configuration profile rather than ad-hoc edits on each machine.
Power users sometimes open TCC.db with sqlite3. Reading that database is itself gated by Full Disk Access — the list of who holds the master key is protected by the master key. Settings is the path that does not require you to already hold it. Prefer Settings.
What Apple’s note does not mean

| Misread | Reality |
|---|---|
| Muse read private messages | Apple did not adjudicate; Meta says both grants are required |
| Dots read your disk by default | OpenAI’s default is a separate cloud computer |
| Claude Code is unsafe without FDA | The dangerous config is quiet: Terminal FDA left on from months ago |
| A prompt replaces the switch | “Do not read my mail” is text; FDA is a bit the kernel checks |
| The new control shipped on 2 Oct | Direction only; no dialog yet |
A stronger model can get worse at obeying a sentence while getting better at finishing a task. The bit in TCC is the part Apple says it will make louder.
If you ship an agent on macOS
| If you are… | Do this before your next release |
|---|---|
| CLI agent author | Document that TCC identity is the terminal; never tell users “enable FDA to fix the error” for repo work |
| Desktop agent author | Split connectors (Messages, Mail) from FDA; default both off |
| IT / MDM admin | Inventory FDA grants; treat terminal apps as high risk |
| End user | Audit the pane tonight; revoke anything that is not a backup |
When Apple’s “very explicit” UI ships, read the dialog. Explicit only helps if you already know what the extraordinary grant contains.
Backup app versus agent: same switch, different blast radius
| Backup app | Agent | |
|---|---|---|
| How it acts | Copies bytes on a schedule you set | Loops until a goal is met |
| What “done” means | The copy exists | The model says the task finished |
| How it picks the next file | A rule list a person wrote | A next-token guess, then a real tool call |
| If it is wrong | You have a bad copy | It may send, delete, or invent a story that does not match the tool log |
That table is why Apple’s note mentions agents even though FDA has existed for years. The permission is old. The holder is new. A harness (Claude Code, Codex, Muse, a dot) shows state, the model emits an action, the harness runs it, and the result goes back in. We walked that loop when covering why OpenAI killed GPT-6.1 Astra; the new fact this week is which computer the loop is holding and which grant is on that computer.
Troubleshooting a “permission denied” on a protected path
| Symptom | Likely cause | Safe fix |
|---|---|---|
| Agent cannot read ~/Library/Mail | FDA off (good) | Do not enable FDA; redesign the task |
| Agent “knows” message text | Connector + FDA, or model confabulation | Check Settings; distrust the model’s story |
| Sandbox on, but FDA still worries you | Two different locks | Revoke FDA in Settings; keep sandbox |
| Cloud agent asks to connect laptop | Optional local bridge | Decline unless the task needs local files |
The fix is almost never “give Terminal the master key so the error goes away.”
Common questions
Does granting Full Disk Access to Terminal give every agent the master key?
For tools you start inside that Terminal, yes for the TCC check. The responsible code is Terminal.
Does Claude Code /sandbox remove Full Disk Access?
No. Seatbelt can limit shell writes and network. It does not clear the FDA row in Settings.
Has Apple shipped the new control?
Not in the 2 October note. No date, no dialog, no API change.
Are OpenAI dots reading my Mac disk by default?
OpenAI’s launch default is a separate cloud computer. The laptop link is opt-in.