MacOS: I get "Ghostty.app would like to access data from other apps" on every launch

[susl]

That popup is annoying as hell :) How do I permanently remove it and is it possible for Ghostty to get rid of it during install?

Ghostty is installed via Homebrew, I have the 1.0.1 version.

[vinerz]

Same thing here. I believe is that Ghostty starts at ~/ home directory. Current solution was to give Ghostty Full Disk Access, but it makes me wonder about its implications. It's a terminal in the end of the day, so disk access makes sense.

[luxargentum]

Does this mean that everyone using Ghostty on MacOS is required to give Ghostty full disk access? What causes this prompt for Ghostty? I haven't seen this with other terminal emulators.

[cowgod]

I also get the popup when I launch Ghostty (presumably as it runs my shell init scripts). However, I also get the popup 5-6 times in a row each time I activate the sesh plugin in tmux to let me switch to a different session (which uses fzf to build a list of directories to switch to -- in other works, disk access). Adding Ghostty to the "Full Disk Access" permission list in System Settings, as described above, did get rid of the warning. That doesn't feel particularly unsafe, as it seems reasonable to me that a terminal would need permission to access any file on disk, but I'm not familiar enough with macOS permissions to know what exactly "Full Disk Access" entails. If there's a more appropriate workaround, I'd love to hear about it.

[stefantrost]

This doesn't seem to be Ghostty specific, I get the same pop up when using iTerm. Accepting or denying it doesn't seem to make a difference. Still, annoying as hell.

[susl]

I don't agree that it's not Ghostty-specific. It is. When launching WezTerm I don't see a popup, even though it does not have Full Disk Access permissions too.

[stefantrost]

I don't get the popup on opening Ghostty or iTerm, but eg when doing a docker build. And that is definitely not Ghostty specific, because, again, I have the same when using iTerm.

[susl]

Maybe it depends on the working dir? Mine starts in home (~), plus I have p10k which might access some other stuff on start. I’ll try without it and report back. But again, with the same zshrc and p10k, Weztern does not ask for permissions Dmytro Suvorov

…

On Sun, Jan 26, 2025 at 11:50 Stefan Trost ***@***.***> wrote: I don't get the popup on opening Ghostty or iTerm, but eg when doing a docker build. And that is definitely not Ghostty specific, because, again, I have the same when using iTerm. — Reply to this email directly, view it on GitHub <#4496 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHSJU2MWR2IUQDRRQ4NR4D2MSVWJAVCNFSM6AAAAABURXTXG6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJVGY4TGNY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[vinerz]

I’d like to add that I also use p10k, pyenv, Oh-My-Zsh with a few plugins and 1Password’s ssh-agent socket setup in my .zshrc.

Haven’t tried other Terminal emulators to check their behaviour though. I can give an update today.

Nonetheless, is it possible to make Ghostty run in a verbose debug log mode so I can track where its access attempt triggers the macOS prompt?