Wrong, bash scripts can pop up a series of permission prompts on macOS if you do a full disk scan. They’re only suppressed when directly run from an application like Terminal that’s already been given full disk access or developer tools permission. In fact, sometimes the syscall just silently fails with no permission popup. For instance I have this python script calling an HTTP endpoint on LAN that when run within tmux would sometimes inexplicably fail with no route to host error because it doesn’t have local network scan permission, there’s no permission prompt, and the only solution is to restart the tmux server.
Not in my case. I only give Terminal and iTerm “Developer Tools” permission. Cursor shows up under “Full Disk Access” with a toggle so it may have requested the permission at some point, but I have it on disable; I don’t see why it needs to reach out of directories I actively open. (And VSCode which I used for years doesn’t even show up there.)
Disclaimer: I’m not sure whether Cursor inherits iTerm’s permissions when launched from CLI. The TCC system is pretty mysterious to me in general.
