mirror of
https://github.com/morluto/rea.git
synced 2026-11-21 14:05:49 +00:00
fix(hopper): explain disclaimed Apple Events responsibility (#12309)
* fix(hopper): explain disclaimed Apple Events responsibility * test(hopper): cover disclaimed Apple Events guidance * docs(hopper): document runtime Apple Events attribution
This commit is contained in:
1 parent
29b2f96f74
commit
0c672c19a9
6 files changed
+78
-39
No files matched your search
@@ -1017,14 +1017,23 @@ stage `connection`.
|
||||
|
||||
If macOS denies Apple Events, REA reports
|
||||
`details.launch_rejection.boundary: "apple_events_authorization"` with
|
||||
`reason: "not_authorized"`, category `unavailable`, and `retryable: false`.
|
||||
Allow the application that starts REA under
|
||||
**System Settings → Privacy & Security → Automation** when that client can be
|
||||
authorized. A hardened-runtime application requires the
|
||||
`reason: "not_authorized"`,
|
||||
`responsibility: "client_or_disclaimed_runtime"`,
|
||||
`settings_pane: "privacy_security_automation"`, and
|
||||
`entitlement_id: "com.apple.security.automation.apple-events"`,
|
||||
category `unavailable`, and `retryable: false`. The helper does not identify
|
||||
the responsible process, so `responsibility` covers both an authorizable client
|
||||
and a client that disclaims TCC responsibility.
|
||||
Allow the application that macOS identifies as responsible for REA under
|
||||
**System Settings → Privacy & Security → Automation**. Some MCP clients, including
|
||||
Claude Desktop, disclaim responsibility, so macOS attributes the request to the
|
||||
REA runtime, such as `node`; changing the client's Automation setting cannot
|
||||
authorize that runtime. In this case start REA from a client macOS can authorize,
|
||||
such as Claude Code or Terminal. A hardened-runtime application requires the
|
||||
`com.apple.security.automation.apple-events` entitlement before macOS will
|
||||
prompt; without it, ask the client developer to add the entitlement or start
|
||||
REA from a client macOS can authorize, such as Terminal. Retrying from the same
|
||||
unauthorized client will not succeed until authorization changes. REA releases
|
||||
prompt; if the responsible client lacks it, ask its developer to add the
|
||||
entitlement. Retrying from the same unauthorized client will not succeed until
|
||||
authorization changes. REA releases
|
||||
the target reservation when the native helper reports its complete authorization
|
||||
rejection after literal argument admission. Before application handoff, REA refuses
|
||||
double quotes, backslashes, or line breaks in the final launcher path or arguments,
|
||||
|
||||
Reference in new issue
Block a user