Warp should request Automation privileges the first time it is run

[HotFusionMan]

Discord username (optional)

No response

Describe the solution you'd like?

Warp should request Automation privileges in System Settings > Security & Privacy > Privacy > Automation the first time it is run, so that the user can grant permission.

Is your feature request related to a problem? Please describe.

I cannot launch BBEdit from the command line to open a document:
>bbedit some_script
>You must allow the application which is running `bbedit` to send events to the BBEdit application.
>Please make appropriate changes in your Security & Privacy system preferences,
or contact your terminal/IDE application's developer for assistance.
bbedit: error: -1743

Additional context

No response

[shrugalic]

👍 Same issue here.

bbedit works fine in Terminal.app, which does have these Automation privileges:

[meyerweb]

I came here to make the same request, for the same reasons. According to Rich Seigel, Warp “is missing an "NSAppleEventsUsageDescription" in the Info.plist.” I thought about adding one myself, but decided potentially warping Warp was not on my list of things to do today.

[siegel]

I thought about adding one myself, but decided potentially warping Warp was not on my list of things to do today.

That would have invalidated the application's code signature, resulting in a warp core breach. Not a good thing.

Devs: you can learn more about NSAppleEventsUsageDescription here.

[leehinde]

I posted a note on this on the Discord server and it scrolled off without a response. Commenting on that here only in case you're tracking interest in the feature.

[gagata]

thanks for the feedback folks!
@leehinde sorry your message got lost on discord and thanks for jumping in here - we do use gh comments / reactions to track interest and prioritize better.

[roballie]

Same issue here. I want to use the bbedit command line tools but cannot.

[berkus]

Same here, cannot launch Hopper via its cmdline tool.

[kevinyang372]

This should be fixed in the latest version of Warp -- feel free to reopen it if there are still some remaining issues