It’s not clear exactly what Apple is going to impose here. In principle, trying to ensure users understand the implications of a permission is good. In practice, Apple is famous for keeping users from making decisions they might reasonably want to make on phones, and it’s starting to creep into the Mac; installing an app Apple hasn’t signed requires the command line, for example.
Yeah I love meta saying “it’s impossible if you’ve denied it access.”
If the user gave it a task and it decided the easiest path forward was just to read his messages, that’s no different than OpenAI agents breaking protocol to find the fastest path to their goal, regardless of side effects (assuming the “permission” was just a request from the LLM rather than a request for full disk access in general from the meta app).
Good change.
Software should not operate at a privileged level “just in case”, but rather have a well-defined functional boundary.
It’s not clear exactly what Apple is going to impose here. In principle, trying to ensure users understand the implications of a permission is good. In practice, Apple is famous for keeping users from making decisions they might reasonably want to make on phones, and it’s starting to creep into the Mac; installing an app Apple hasn’t signed requires the command line, for example.
It doesn’t, but it does make a scary popup, and requires the user to know to go to settings to find the section to override that popup.
Yeah I love meta saying “it’s impossible if you’ve denied it access.”
If the user gave it a task and it decided the easiest path forward was just to read his messages, that’s no different than OpenAI agents breaking protocol to find the fastest path to their goal, regardless of side effects (assuming the “permission” was just a request from the LLM rather than a request for full disk access in general from the meta app).