With the browser integration now working for me, I noticed that unlocking and immediately using (to fill in some credentials) is now 1 more step than before (using Firefox):
Without integration, I used shortcut to open the extension, type my master password (in the extension's window), and then select the item for filling in.
Now with integration, I use the shortcut to open the extension, type my master password (in the application's window which pops up instead of the extension's window), but then I have to again use the shortcut to open the extension window before being able to select the item.
It would be great if after unlocking (triggered by the browser extension) the browser extension window would also show up (with focus), so that apart from typing the master password in a different window it feels the same as without integration.
(Apart from the above, after I got the integration working I initially got bitten by a left over setting in the setting.json file that is no longer visible in the application but apparently still used. I used to have
"security.autolock.onWindowClose": true in those settings. As a result, after typing my password in the application's window and hitting enter, the application immediately locked itself again - and thus the browser extension. At first I only got the browser extension to usable (unlocked) state by opening the application, unlocking, and leaving that window open. But then I realised I may have some old setting lingering around.
I can imagine that more early beta testers run into this, so perhaps you should check (or warn) about that setting when someone enables the browser integration.)
1Password Version: 8.0.33-79.BETA
Extension Version: 1.24.2
OS Version: Ubuntu 18.04 LTS
Sync Type: Not Provided