I upgraded to 1Password 8 yesterday. Since upgrading extensions in Firefox and chrome not working.

Jack_P_1P , I tried using the 1password in app about 6mo after it went live. It was slower, more cumbersome, required me to do multiple unlocks for each browser (firefox, safari, chrome, & edge. Not to mention updating one would throw the other out of sync for a few mins. If I was working offline or in secure mode at work with no connection to 1password.com allowed at all. They just do not work and I work 7-10hrs a day where my work computer is blocked from accessing 1password.com. So I have to rely on what is stored locally and I need it to be available to all browsers when I make a change. 1password8 & 1password in browser cannot do that by design, its less secure. Also most companies doing security frown on having multiple streams for the same thing running on a PC. Over all Its a very wasteful system design that isn't efficient, clean and can be well controlled. So with managed systems several companies just don't allow it because they can't be 100% secure with a browser plugin that requires connecting to an external off machine database. What it basically boils down to is 1Password management doesn't want to maintain 2 variations of browser plug-ins because it cuts into profit margins. And that is a numbers manager trying to make his numbers look better then they actually are. In the long term, dropping efficient local access web plug-ins and concentrating on bandwidth using stand alone mini browser app plug-ins is going to hurt your business and eventually lead to a security hack. It's only a matter of time till hackers add in sniffers to plug-in to gather raw data so they can learn how to access the 1PW in app plugin directly since it requires a internet connection to work. It is much harder to hack a system that works like a Hashi Corp vault running on the local machine with apps directly connecting to it on the same silicon.