Forum Discussion

subsonic_rumble's avatar
subsonic_rumble
New Contributor
7 hours ago

Beyond frustrated - 'op' detects no accounts?!?

Between the https://github.com/1Password/shell-plugins/issues/122#issuecomment-2183950261 and now this, 1password-cli is frustrating to use and has sucked more time out of me than helped.

According to https://developer.1password.com/docs/cli/app-integration/ enabling CLI integration should automatically cause "op" to detect 1Password on my machine. It worked exactly once and broke after the most recent updates to 1password-cli and 1Password app. it is now prompting me to manually add an account:

% op -v
2.33.0
% op vault list
No accounts configured for use with 1Password CLI.

 - Turn on the 1Password desktop app integration to sign in with the accounts you've added to the app: https://developer.1password.com/docs/cli/app-integration/ for details.
 - Add an account manually with 'op account add' and sign in by entering your password on the command line. See 'op account add --help' for details.
 - Authenticate using a 1Password service account by setting the 'OP_SERVICE_ACCOUNT_TOKEN' environment variable to your service account token. Learn more: https://developer.1password.com/docs/service-accounts/
 - Use 1Password CLI with a Connect server by setting the 'OP_CONNECT_HOST' and 'OP_CONNECT_TOKEN' environment variables to your Connect host and token, respectively. Learn more: https://developer.1password.com/docs/connect/

1Password for Mac version 8.12.8 (81208026).

macos

2 Replies

  • taylorbrooks's avatar
    taylorbrooks
    New Member
    1 hour ago

    I’d sanity check whether the desktop app and CLI are effectively talking to different installs or different runtime contexts. I’ve seen weird behavior after updates when the app is current but the shell is still resolving an older binary, or when the shell session predates the app integration toggle.\n\nA few low-friction things I’d try before going deeper:\n1. Run `which op` and make sure it’s the binary you expect.\n2. Quit 1Password completely, relaunch it, then open a brand new terminal session instead of reusing an old tab.\n3. Toggle the desktop app integration off and back on, then retry.\n4. If you use Homebrew, reinstall or relink the CLI so you know the binary and app are in a clean state.\n\nIf `op account add` works manually but app integration still doesn’t, that feels like a desktop-app handshake issue rather than an account problem.

  • 1P_SimonH's avatar
    1P_SimonH
    Icon for Community Manager rankCommunity Manager
    1 hour ago

    Hi subsonic_rumble​ 👋

    I'm sorry this has been such a time suck for you! I collected some suggestions from the team, but if you want, you can email mailto:support@1password.com and we'll get you set up with a phone call so you can talk through this with an expert. If you go that route, just reply here with the ticket ID so we can get the call coordinated.

    If you want to try a couple other things, here are the suggestions I received:

    • If you haven't yet, try a reboot of your computer. A coworker said they ran into this issue and a reboot resolved it.
    • We released a new beta of the CLI on March 16, so if you haven't updated yet, update to the latest version.

    • Double-check you're following the guidance here (making sure you have the setting enabled in the app): https://developer.1password.com/docs/cli/app-integration/

    • Try setting up the optional variable documented here: https://developer.1password.com/docs/cli/app-integration/#optional-set-the-biometric-unlock-environment-variable

    Again, I'm sorry for the trouble and hope to hear from you.