It's likely that in time other software will "learn" (or be "taught") about 1Password's new authentication behaviour. This is a "chicken and egg" problem: if we don't release these authentication improvements, no one will ever adjust to them. But if we do, other software may be unprepared and have a bad interaction with 1Password. However, if we do nothing at all so we can avoid disrupting anyone's workflow, forego making these changes, and you or anyone else fall prey to an exploit down the road, you'd (rightly) point an angry finger squarely at us for failing to act in a responsible manner. Although this is necessary, I apologize for the inconvenience this has caused you and others. And of course we're here to help. There are a lot of folks out there who aren't having these issues because there's nothing stopping 1Password from connecting securely to the browser, but of course there are some who are affected. I'm sorry that you're among the latter group who are suffering from this. But we'll help you get this sorted out. Please let me know what you find when trying the suggestions above. I look forward to hearing back from you!