Repository navigation
"op completion zsh" causes OS X "would like to access data from other apps." warning #586
Description
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.
Activity
renet10 commentedon Mar 5, 2026
*** Edited for clarity ***
I spoke too soon. The "allow access" warning now pops up again for iTerm2, but only once when the app is started. Subsequent windows / tabs do NOT trigger the warning even though .zshrc is sourced. It is possible this is not new behaviour, since I did not restart iTerm when I toggled Full Disk Access on/off. However I was definitely receiving per window/tab warnings before toggling Full Disk Access.
Note I also only receive a single warning from VS Code no matter how many sub-shells I start.
tiktax commentedon May 30, 2026
Related: I've opened #606 which covers a more specific variant of this issue — op probing Apple Events IPC unconditionally when using a Service Account token from a LaunchAgent context, even with
OP_CACHE=falseandOP_BIOMETRIC_UNLOCK_ENABLED=falseset. The secrets resolve successfully without TCC approval, confirming the probe is architecturally unnecessary when SA auth is configured.