Have the CLI be unlocked in tandem with gui.

Options
jhogendorn
jhogendorn
Community Member

If the desktop app is unlocked, it would be good to be able to configure the cli to also act unlocked.

When the cli is called in subshells and other scenarios (ie its part of a script something calls, its a few layers deep and its not sharing the same environment as the user-level shell) it will prompt for biometric auth. This is fine, but it is a bit annoying in some instances. I wouldnt mind if it was just the first time, and a timeout could relock it, but because its tracking that unlock status in its local environment, and each time that env is new, it always prompts.

An example is that I use chatgpt in neovim, and i've configured it to use the 1p cli to retrieve the OpenAI key. Every time I open the dialog, I am prompted for bioauth.

It makes some amount of sense that if the desktop app is unlocked, the cli could be unlocked as well. Thoughts? Alternatively a more persistent way of the cli remaining unlocked thats independent of shells.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided