I find myself frequently having this same issue, and I have a hard time believing this is the intended workflow. I think I figured out what's happening, though.
After upgrading to 1Password 8, I often find that hitting ⌘-\ to autofill does ... nothing. Sometimes it works, but many times it doesn't, which is obviously frustrating. I expect to be prompted to unlock, place my finger on the TouchID sensor, and then watch the fields get autofilled. (Needless to say, this worked flawlessly with 1Password 7 every time.)
This always catches me off-guard, so then I move my cursor to click on the tiny 1Password icon. Then I'm reminded that I need to "press the 1Password icon in your browser's toolbar to unlock." (But why?) So then I move my cursor again and click the other icon.
This launches 1Password, which immediately quits itself — which is weird, but okay — and then after a moment I can use TouchID to proceed. Obviously this is not a very slick experience.
What I've noticed is that while I have 1Password open, this all works as expected. Hitting ⌘-\ will instantly prompt me to unlock with TouchID and then autofill. If I close 1Password using the close button on the window, this sometimes stops working ... but not always. If I quit 1Password with ⌘-Q, it never seems to work anymore. I know in the past there were some options like "Quit 1Password Completely", but I can't seem to find those anymore, and if this new behavior is intentional, it's extremely confusing.
As it happens, I'm frequently opening the 1Password 8 app (using a keyboard launcher similar to spotlight) and closing it using the keyboard (⌘-Q) due to limitations and problems with the new universal search and browser popup. So I guess that's what's triggering the issue for me, but I'm still very confused about what's expected and what's buggy behavior.
Thanks in advance for any help with this issue.
