macOS Full Disk Access for developers: how it works and what Apple is changing

Apple’s note says Full Disk Access largely sidesteps the privacy controls behind its APIs, so that backup apps can work on the Mac. Some developers, it says, use the permission in ways that could expose everything on a system, including files, mail, messages and browsing history, without users fully understanding it, and for communication apps that also affects the people users talk to. Apple will introduce additional controls so that users who genuinely want to grant this level of access can only do so with very explicit user action, and it ties the change to AI agents becoming more capable and autonomous. The post names no macOS version, date or new API, so treat any specific timeline you read elsewhere with care until Apple publishes one.

Command-line tools do not get their own entry in most cases. When you grant Full Disk Access to Terminal or another terminal app, the commands you start inside it run with that access, which is why a script fails with «Operation not permitted» in one terminal and works in another. Coding agents and automation tools that run shell commands inherit whatever their host app has. That is exactly the pattern Apple’s note points at, so grant it to the narrowest app that needs it and remove it when you are done. For agent tooling on the Mac, see Xcode’s MCP server with Claude Code and Codex.

A remote shell does not inherit the Terminal grant on the Mac. In System Settings > General > Sharing, click the info button next to Remote Login and turn on Allow full disk access for remote users if remote sessions need it. It applies to everyone allowed to log in remotely, so limit Remote Login to the users who need it.

macOS has no supported command that grants Full Disk Access. tccutil reset SystemPolicyAllFiles com.example.app clears the decision for one app, and without a bundle ID it clears it for all apps, so the next access triggers the normal flow again. That is useful in testing: reset, then check that your app explains why it needs access and opens the right settings pane.

Organizations grant it through a Privacy Preferences Policy Control profile from their MDM. The service key is SystemPolicyAllFiles, which Apple describes as access to all protected files, including system administration files, and the profile identifies the app by bundle ID and code requirement. Not every privacy service works that way: for screen capture and listening to input events a profile can only deny access, not grant it. If you sell to businesses, document the bundle ID and code requirement your customers’ IT teams need.

Ask whether you need Full Disk Access at all. Many tasks are covered by narrower routes, such as files the user picks in an open panel or security-scoped bookmarks to folders they chose. If you do need it, as a backup or sync tool might, say why in plain words before sending the user to Settings, keep working with reduced features when access is missing, and test the flow after tccutil reset. Then watch the release notes for macOS 27.2 and later for the new controls. For the current beta, see what’s new in the 27.2 betas.

A Mac app users trust with their data keeps them; being found brings new ones. Censuus ranks apps by visits and sponsorship, and adding your app is free on the List my app form. Apps climb on the visits they draw, and a sponsor can pay to rise higher.