We want your feedback on biometric unlock!

@XIII can you give us some more details about the context where that happened? Is it a persistent issue? From what I understand, this happened while you tried to run a CLI command, while the 1Password application was not running? Did this happen on the nightly version you were running before, or on the current one?

It happened only once.

However, biometric unlock is now completely broken again (see my post in another private beta; I'm not sure what I am allowed to post where).

Fixed! Thanks!

Hi @smanojkarthick, sorry about the slow reply here. I just noticed we hadn't yet responded to your feedback about using Biometric Unlock in multiple terminals.

One minor piece of feedback: I use multiple panes and windows in my terminal, so it would be great if the Biometric unlock didn't show an allow prompt for each of them. It's not a big deal and I figured there's probably a good reason for why it does - but thought I'd share it either way :)

Unfortunately, you're right and we do have a reason to do this. For your security, we want only the terminal to have access to your 1Password account and not any process on your machine. Since any process can start a terminal, we have to lock access down to a single process of that terminal.
This is to limit the attack surface to access your 1Password account. If for example an npm dependency of one of your side-projects contains a backdoor that allows code execution, this cannot be used to access your 1Password account, because execution of CLI commands will need re-authentication for the new process.

I hope this sheds some light on our reasoning.

Thanks for detailed explanation!