CLI hangs when requesting items

Hi there,

I'm experiencing the same issue with all plugin commands, but one thing that hasn't been mentioned, is that the failing op read does prompt me for a login (put up a unlock screen and accept my fingerprint) before i hangs, and if i break the command with ctrl+c and run the exact same op command again, everything works just fine, since i'm already logged in to 1Password - which also might explain why running 1Password in the menu helps in some cases, since it might keep the login session running a bit longer...

Update: Just updated to latest CLI version (2.26.1), and so far it seems to be working quite a lot better

1. What command(s) are failing? "op --account https://companyname.1password.eu signin" but also every other command which requires re-authentication
2. Do you have 1Password set to appear in your menu bar / notification area / task bar? yes
3. Is 1Password running but locked, running and unlocked, or not running at all when you run the command(s)? running, and i guess locked because of the re-authentication
4. What operating system are you running? MacOS Sonoma 14.3 (23D56)
5. What shell are you running? bash script within zsh
6. What version of 1Password the app and op are you running? 1Password for Mac 8.10.28 (81028034) + op 2.24.0
7. Do you have biometrics enabled to unlock 1Password? yes

Hi tamird,

I do not have public progress to share though I can confirm our team is actively working on the issue and has been able to reproduce more of the above scenarios.

Hopefully they will find a solution soon.

Hello, it's been a few months now. Any progress?

Hi ecerulm,

Thanks so much for for the answers to those questions, I have added you as an impacted user and shared the details and your reproduction steps with our developers.

I'm also experiencing this.

Im on macOS Sonoma 14.3.1

I can reproduce 100% of the time, by

1. Closing down both 1Password app and 1Password in the menu bar
2. Start 1Password again (that opens both the app and the 1password menu bar. I leave it locked
3. From kitty or iTerm or Terminal , I run op --debug --cache=false read "op://Personal/xxxx"
4. It will pop up the "1Password Access Requested" I use the Autorize with Touch ID
5. I see the 1Password desktop app unlocking
6. But the op read hangs forever
7. If I kill it and run it again it will works (presumably because 1Password is already unlocked)

Responses to your questions Joshua_ag

1. What command(s) are failing?
   • op --debug --cache=false read "op://Personal/xxxx"
2. Do you have 1Password set to appear in your menu bar / notification area / task bar? yes
3. Is 1Password running but locked, running and unlocked, or not running at all when you run the command(s)?
   • Is running locked (both the app and the icon menu bar are visible)
   • when the app is unlocked then op read won't hang for me.
4. What operating system are you running? macOS Sonoma 14.3.1
5. What shell are you running?
   • I tried both zsh and bash, in macOS Terminal, kitty and iTerm2
6. What version of 1Password the app and op are you running?
   • op --version 2.25.0
   • 1Password for Mac 8.10.27 (81027003)
7. Do you have biometrics enabled to unlock 1Password?
   • yes, I use TouchID

```
op --debug --cache=false read "op://Personal/xxxx"
9:19AM | DEBUG | Session delegation enabled
9:19AM | DEBUG | NM request: NmRequestAccounts
9:19AM | DEBUG | NM response: Success
9:19AM | DEBUG | NM request: NmRequestAccounts
9:19AM | DEBUG | NM response: Success
9:19AM | DEBUG | account not signed in, filter= latest_signin_user=xxxxx
9:19AM | DEBUG | NM request: NmRequestAccounts
9:19AM | DEBUG | NM response: Success
9:19AM | DEBUG | NM request: NmRequestAuthorization
9:19AM | DEBUG | NM response: Success
9:19AM | DEBUG | NM request: NmRequestAccounts
9:19AM | DEBUG | NM response: Success
9:19AM | DEBUG | NM request: NmRequestDelegatedSession

```

Hi tamird,

No not yet, still investigating. Hopefully the developers can figure out things soon.

Joshua_ag any updates on the op plugin issue?

Thank you @tannerellen and @iwehrman,

I have passed along these details to the development team. We really appreciate the help!

Thanks Joshua_ag. One thing I've noticed is that this failure started happening much less frequently after enabling 1Password in the menu bar. To your other questions:

• op item get
• I do now, and it still occasionally fails. Before I enabled this, it failed on the initial request most of the time.
• Typically running and locked. But failures sometimes happened when running and unlocked.
• Mac OS 14.2.1
• fish 3.1.2
• 1Password 8.10.23 and op 2.23.0
• Yes, Apple Watch is set to unlock.