Windows CLI session

Hi all,

I've been happily working with the 1password CLI for some years now. On Windows, Linux and lately Mac. When the app authentication integration released I was quite stoked that I could now use biometrics/windows hello in my sessions.

I've been integrating op commands in various scripts of mine, and I've been noticing that the session doesn't work at all when using this app integration on Windows (maybe also Mac/Linux, but didn't test it there), or that I just don't understand how it works. 

I've read all the limitations and issues people are having with subshells, the --session and the --raw parameters not working, but that still does not explain why doing multiple commands in a single script or terminal session should ask for authentication every command it does.

Multiple use cases;

1. I open a new terminal session. I enter some command like op item list. I get asked to signin by the app using windows hello. I signin, and I the command executes successfully. If my understanding is correct, this should authenticate my current terminal for 10 minutes. However, if I immediately enter the command again, I have to authenticate again.

2. I have a simple powershell script. In that script, I execute an op item list command twice. So for example my script.ps1 can look like;

$items1 = op item list
$items2 = op item list

No weird things with subshells or whatever, so I would expect 1 prompt for the authentication on the first command, and for the second it should already be authenticated. However, I get 2 authentication prompts.

So my question; do I misunderstand how this authentication using the app integration should work in a single shell or script, or is this some bug? Is there a workaround (without having to disable the app integration)

I'm using the latest 1password cli -V2.32.0- and 1password app - 1Password for Windows 8.11.12 (81112027). I've also noticed this behaviour on multiple windows devices.