This article may contain affiliate links. Learn more on our Partner Program page.
In early October, Apple announced that it would only grant full disk access on Macs after a very explicit action. The company didn't specify what this action would entail. The first beta of macOS 27.3 now contains code that provides an initial answer – still disabled, but surprisingly concrete.
The changes were discovered by code analyst pdfu, who examined the first beta of macOS 27.3 and described his findings regarding full disk access on X. They relate precisely to the permission that Apple addressed in its developer announcement of October 2nd.
Apple had announced stricter controls for full disk access, citing the growing risks posed by AI agents as the reason for the haste. Granting this access opens almost the entire Mac to an app, including emails, messages, and browsing history. Apple did not specify the version, timing, or expiration date, only the target:
In the future, we will introduce additional controls so that users who truly want to grant an app this exceptional level of access can only do so through a very explicit action.
The code in the macOS 27.3 beta shows how Apple could implement this. The discovery of the feature in the code is documented, not the exact time when Apple might activate the change.
Key Facts at a Glance
- The first beta of macOS 27.3 includes a feature change that prevents apps from automatically being added to the list for disk full access.
- Users would then have to add an app themselves via the „Add“ button or by dragging and dropping it from the „Programs“ folder.
- There are currently no additional warnings or dialogue options, but the name of the functional switch suggests otherwise.
- Also new in the code is a feature for sharing individual folders called „Private Folders”.
- In Beta 1, the function switch is deactivated; for users, nothing changes for the time being.
How an app gets on the list today
If an app wants to read a protected file without full disk access, macOS does not ask the user for permission. The system denies access and stores this denial in the database where it manages data permissions.
This causes the app to appear under System Settings > Privacy & Security > Full Disk Access, with the switch turned off. Many apps use this tactic: After such an access attempt, they appear in the list and prompt the user to open the settings and toggle the switch.
More than this one switch is not needed for full access today.
What the code changes in macOS 27.3
With the new feature enabled, macOS no longer saves these automatic rejections. The app will then not appear in the list automatically. Users who want to grant it full disk access must add it manually – either by clicking the „Add“ button (+) below the list or by dragging the app from the Applications folder.
The functional switch, in its current version, does not include any further warnings or dialog boxes. However, its name contains the word for warning, suggesting that such messages will be included in later beta versions. According to pdfu, it is disabled in Beta 1.
„Private Folders” as a narrower release
macOS 27.3 also includes a new permission called „Private Folders.” It's set up like full disk access, but applies folder by folder. According to pdfu, it's not yet fully integrated.
The new feature also applies here: If it's active, macOS won't save automatic denials for these folders either. This could make permissions a more restrictive alternative to full disk access. An app would then have access to specific folders instead of almost the entire Mac.
One more step is no protection
I consider the change a sensible first step, but not yet the very explicit action Apple announced. An app can still guide users through the settings with instructions; in the future, it will only have to explain how to add the app via „Add“ or drag it into the list. This adds one step, but doesn't change the fact that ultimately, a single permission opens emails, messages, and browsing history.
More significant is the „Private Folders” feature. Sharing per folder would allow an app to access only the portion it needs for its task. Since both changes rely on the same functionality, I expect Apple to activate them together, rather than the stricter full disk access permission alone.
Until then, everything remains the same on your Mac. If an app with the switch enabled is in your list, it already has full access.
Is an extra step via „Add“ enough of a hurdle for you – or would you only grant an AI agent access if you could restrict it to specific folders? Let us know in the comments how far you would allow an agent to go on your Mac.
