I don’t quite understand why people complains this is bad for AI agents. Local Code (<a href="https://releases.drawthings.ai/p/public-beta-of-local-code-by-draw" rel="nofollow">https://releases.drawthings.ai/p/public-beta-of-local-code-b...) doesn’t require full disk access, when you ask the agent to deal with some files it doesn’t have access to, the built-in ‘permit’ tool will trigger the OS folder grant interface and that information will be recorded both by Apple and by the app so it can be revoked later if you want. That allows you to not give full disk access to the app to be useful.
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 granted zsh or bash or python or any goddamned thing you can run in a shell FDA.
It is! The directory grant is once and the sandboxed app can save the bookmark for the future access. As a agent program, you can display this so users can revoke / temporarily disable access for a period of time: <a href="https://developer.apple.com/documentation/foundation/nsurl/startaccessingsecurityscopedresource()?language=objc" rel="nofollow">https://developer.apple.com/documentation/foundation/nsurl/s...
Agree, I think for CLI harness, there is no good alternative, you either have access permit per terminal app (which is not ideal), or I guess that is what Apple means they will "address" it?
Because it's deeply annoying/unenjoyable to have to click "Allow" in the middle of a flow, especially if you're not at the time actually _at_ your computer?
Just add to system prompt: “ask permissions for files and folders you might need upfront. Don’t annoy users with permission request in the middle of the flow.”
In fact, my pet peeve is why can't 1Password build in the ability to "remotely" approve something via the 1Password app? I'd get a push message, hit allow, and it does the negotiation in an e2e encrypted way.
Then I could approve something my agent needs when I'm not at the computer. Service Accounts are a crappy solution to be honest.
liuliu · · focus · HN ↗
wpm · · focus · HN ↗
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 granted zsh or bash or python or any goddamned thing you can run in a shell FDA.
liuliu · · focus · HN ↗
Agree, I think for CLI harness, there is no good alternative, you either have access permit per terminal app (which is not ideal), or I guess that is what Apple means they will "address" it?
tannertech · · focus · HN ↗
[dead]
tekacs · · focus · HN ↗
liuliu · · focus · HN ↗
atonse · · focus · HN ↗
In fact, my pet peeve is why can't 1Password build in the ability to "remotely" approve something via the 1Password app? I'd get a push message, hit allow, and it does the negotiation in an e2e encrypted way.
Then I could approve something my agent needs when I'm not at the computer. Service Accounts are a crappy solution to be honest.