op - Allow Access Modal prevents me from unlocking

Hi @iamnoah , thanks for your feedback! I am having trouble reproducing your use case here. The modals you are talking about are biometric unlock modals right? You could check this by going to Preferences> Developer > CLI2 and see if Biometric Unlock is ticked. Usually this should ask for your fingerprint (if your device supports reading fingerprints, otherwise it falls back to manual input of the system password) and once unlocked it should unlock both your CLI and your desktop app. If you were to disable biometric unlock, then each command that would require authorisation through a modal in the past, would now fail telling you to sign in. Would this be a more desirable use case for you?

All in all, even if we assume that the modal and 1Password desktop app do not go into this partial deadlock you described, the modal would have to appear for every command that spawns after 10 minutes since the last command executed, because this is the documented length of an auth session (when using biometric unlock, it is 30 minutes when biometric unlock is off). The only way you could overcome this is to use a Connect Server or wait for the release of our Service Accounts beta feature, which both allow for persistent authentication via environment variables.

Hope this helps a bit and looking forwards to your answer,
Andi