Make Bitwarden's detection when to save a (new or changed) password more robust

I got Bitwarden with the idea that across all devices, it seamlessly detects when to save a password and when to enter one. In addition, it should not ask to save passwords when that is not needed (i.e. the password is up to date).

Instead, I constantly have to manage Bitwarden as it often fails to detect when a password is entered, has to be entered, a new one is generated, and so on. I then have to enter the master key, find the relevant site, click, click some more, paste the password, and so on.

When creating new accounts, it also often does not save the password, especially for websites that have two separate pages for email and password specification. Or it saves just the password and fails to enter the email address.

In the end, I am constantly managing Bitwarden and filling in the gaps that should be filled automatically. If Bitwarden cannot 100% of the time detect when to act (and sure, builtin browser pw managers don’t either, but those are free, and they don’t add extra steps to the login process), I really don’t see why I should use it.

@Jan_M Welcome to the forum!

  1. I changed the title of your request from “Bitwarden’s detection when to save a password is not robust” to “Make Bitwarden’s detection when to save a (new or changed) password more robust” as the latter expresses better what your request actually is.

  2. Though I can understand your request - the recommended method (we also in the community constantly recommend) is, to first (or parallel) create a new login item in Bitwarden - and to then create your new account on the site with that. And when you do that, you can deactivate “Ask to add login” and “Ask to update existing login” in Settings → Notifications, and you have a much more consistent experience with Bitwarden. (though, probably you need time to adjust to that new “flow”)