also looking at this
Claude/app issues review e7f207
#16
8 files
+112
-35
| @@ -71,6 +71,16 @@ A manifest is strictly validated and cannot run code, reach the network or read | ||
| 71 | 71 | and `{clipboard}` are filled in when a snippet is used. `function ea(){return new Xo}` stays literal. The |
| 72 | 72 | clipboard is read only if the snippet asks for it. |
| 73 | 73 | |
| 74 | **Granting Automation.** The Automation pane has no way to add an app. Launchpad appears | |
| 75 | there only after macOS has asked, and each app it controls (Finder, System Events, Contacts, | |
| 76 | Calendar) is its own switch under the Launchpad row. So the first grant is the prompt itself: | |
| 77 | choose OK. If you chose Don't Allow, open System Settings > Privacy & Security > Automation and | |
| 78 | switch that app on under Launchpad. If Launchpad is not listed at all, nothing has asked yet; | |
| 79 | `tccutil reset AppleEvents com.stacksjs.launchpad` clears the record so the next attempt asks | |
| 80 | again. Emptying the Trash also depends on the Finder warning in Finder > Settings > Advanced: | |
| 81 | leave it on and answer the Finder dialog, or turn it off and let Launchpad's own confirmation | |
| 82 | stand alone. | |
| 83 | ||
| 74 | 84 | **Builds.** Direct downloads are hardened and carry the Apple events entitlement, which macOS |
| 75 | 85 | requires before it will even ask for the Automation permission. A sandboxed Mac App Store |
| 76 | 86 | build does not have that entitlement, and the sandbox can also stop Spotlight file search, so |