op CLI version
2.32.1
Goal or desired behavior
On OS X Tahoe 26.3 (25D125).
Do not want the op command to trigger an OS X warning.
Current behavior
As recommended by 1password-cli, I have eval "$(op completion zsh)" in my .zshrc. A week or so ago I noticed that whenever I started a new iTerm2 window, I would get the OS X popup warning:
iTerm2 would like to access data from other apps.
No matter whether I clicked Allow or Deny, this popup would appear whenever I started iTerm or created a new tab or window.
I would also get this warning whenever I typed the "op" CLI command. In fact, all I had to do was type op<TAB> to get the completions and it would pop up the warning.
Strangely though this warning would NOT occur with OS X Terminal.
In my Mac System Settings, I have Full Disk Access turned OFF for both iTerm2 and Terminal. Just for laughs, I enabled Full Disk Access for iTerm2, and the warning did not appear.
Strangely enough however, once I turned Full Disk Access OFF again for iTerm2, the warning NEVER reappeared
Now however I noticed I am getting warnings whenever I start Visual Studio Code as well. Commenting out the op command in .zshrc again removes this issue, but I do not want to toggle Full Disk Access on/off.
It is not clear whether this is an op issue, OS X issue, or both.
Relevant log output
op CLI version
2.32.1
Goal or desired behavior
On OS X Tahoe 26.3 (25D125).
Do not want the
opcommand to trigger an OS X warning.Current behavior
As recommended by 1password-cli, I have
eval "$(op completion zsh)"in my .zshrc. A week or so ago I noticed that whenever I started a new iTerm2 window, I would get the OS X popup warning:No matter whether I clicked Allow or Deny, this popup would appear whenever I started iTerm or created a new tab or window.
I would also get this warning whenever I typed the "op" CLI command. In fact, all I had to do was type
op<TAB>to get the completions and it would pop up the warning.Strangely though this warning would NOT occur with OS X Terminal.
In my Mac System Settings, I have Full Disk Access turned OFF for both iTerm2 and Terminal. Just for laughs, I enabled Full Disk Access for iTerm2, and the warning did not appear.
Strangely enough however, once I turned Full Disk Access OFF again for iTerm2, the warning NEVER reappeared
Now however I noticed I am getting warnings whenever I start Visual Studio Code as well. Commenting out the
opcommand in .zshrc again removes this issue, but I do not want to toggle Full Disk Access on/off.It is not clear whether this is an
opissue, OS X issue, or both.Relevant log output