Updated MacOS 27, CLI now says No Accounts configured for use

Forum|Forum|15 days ago
September 15, 2026
5 replies
17 views

The desktop app is setup with “Integrate with 1Password CLI”

CLI access was working prior under MacOS 26.x.x

macOS

Update: Setting the BIOMETRIC environment variable addressed the issue.

https://www.1password.dev/cli/app-integration#if-you-see-a-lost-connection-no-accounts-configured-or-connection-reset-error

B

ben_chmark1

thanks just wanted to say this helped me when I had the same issue 👍

I hope that this is a bug and isn’t the intended behaviour, as I prefer not to have to use TouchID, but also don’t want to have to input my password directly in the CLI every time I want to use `op`

1P_Dave

1Password Employee

Hello @skasch and @ben_chmark1! 👋

Our developers are aware of an issue on macOS 27 where users might see “No account configured” when using the 1Password CLI. We’re currently investigating.

For the time being, the solution is to give Terminal access to data shared from 1Password on macOS 27:

Open macOS System Settings.
Click Files & Folders. Select the Terminal App.
Select "Data shared from 1Password for Safari and related apps".

If anyone discovers that this doesn’t work then let me know.

-Dave

T

tom_nmg

So, I'm getting the same issue and your suggestion to add the permissions to the terminal app does not seem to work for me at least.

I am using iterm2 with a ZSH terminal.

Opened macOS System Settings
Selected privacy and security
Selected files and folders
Selected the iTerm app
Activated the option for data shared by 1password and affiliated apps
Restarted iTerm and still got the same issue

CLI version 2.39.0

macOS Version 27.0 (26A428)

iterm2 Version 3.7.3

Both the CLI and iTerm2 were installed through Brew and it was working just fine in the new version of macOS for the last several days, but when I did the brew upgrade this morning is when it broke. Unfortunately, I haven't been able to find a combination of older versions or config to get it to work again.

Both the standard terminal app and the terminal built into VS Code are still working just fine with the CLI. It seems to be isolated, at least for me, to iTerm2

B

ben_chmark1

This approach has worked for me, at least for the time being - I am also using iterm2 with a ZSH terminal.

Also on CLI version 2.39.0, macOS Version 27.0 (26A428), iterm2 Version 3.7.3. 1Pass CLI installed via brew, but iTerm2 was not.
Perhaps something to do with the brew-managed iTerm2 and how that interacts with macOS’s permissions management?

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO