[API Feature Request] Permissions

[kylemh]

Describe the feature and the current behavior/state.
Extensions could potentially wish to do things that would require the user to give Raycast more permissions. For example, if I wanted to create an extension that needs to query all of a user's text messages in iMessage, they'd need file system access. Currently, my only recourse is to show a UI to the user instructing them they need to do this.

I would like to request that permissions requests are somehow made into a more 1st-class experience. Both for extension authors and for Raycast users.

Will this change the current API? How?
Potentially! I could see a future where any Mac permission error simply triggers a permissions request; however, imperatively using a "Permissions API" through Raycast could enable things like fallback behavior specific to that extension.

Who will benefit with this feature?

• Extension authors who wish to create extensions that require more permissions than the user has initially provided Raycast
• Users who want to continue enjoying Raycast's 1st-class experience surrounding permissions requests.

[loris]

Also interested in this (needs Full Disk Access, to read Safari Cloud Tabs).
It would be great if one could specify some permissions in an extension package.json and Raycast would check for them and handle the display of instructions as it already do when you try to access browser bookmarks:

[blabberlicious]

I'm getting this error when trying to use your Extension, or any that tries ti access Safari Bookmarks.
Recently update to Sonoma.

Thanks!

Error: maxObjectCount exceeded

We.parseBuffer:bplistParser.js:92:10

---

89: }
90:
91: if (numObjects > exports.maxObjectCount) {
92: throw new Error("maxObjectCount exceeded");
93: }
94:
95: // Handle offset table

Ty:search-bookmarks.js:51:24532
search-bookmarks.js:51:25074
FSReqCallback.readFileAfterClose:read_file_context:68:3