Basically broken, like, apparently, all third-party password extensions.

Often doesn't find passwords for sites. Tells you every single time that you've updated the password and asks if you want to resave it, so you have no way to tell if the password has actually changed. It always says it has, whether it has or it hasn't.

Can't find TOTP codes even when they're in Keepass, you have to go copy them by hand.

All-around seems like a half-finished, "beta" release that is almost ready for use, but not quite.

It is extremely nerve-wracking to constantly be told the password has changed, and have to stop and think about whether it has and whether you want to save it, every single time you log into a site. Worse, you can only see this before you have logged in, before you know if the login was any good... it disappears as soon as you're in.

So, basically, it keeps you on your toes, always keeps you guessing and uncertain about what's going on... exactly what you DON'T EVER WANT A PASSWORD MANAGER TO DO.

Extremely disappointing.

EDIT: Response to the developer's comment below: The user guide, which is one mammoth long page from a page 2 or 3 levels deep on the website, contains one instance each of the phrases "new password" and "banner", neither telling me anything about how to fix this. I searched for the word "changed" too, that doesn't appear anywhere in the document at all.

Also, when you do need to use that banner, the buttons don't do anything. Click them, they sit there. Did they work? Did they not? Did anything get saved? No way to know.

I truly hate to criticize a FOSS project but this is really just awful design, to the point I don't trust this thing. If I don't know when passwords are new or not, or whether it's saving them or not, and I have to scour a huge 12,000 word single-page wall of text that doesn't turn up the information I need even when I search it for the specific terms the developer told the manual would instruct me on, so I can't find the new password banner settings by searching for "new password" or "banner" then, sorry, I have to nope out on it. I'm just not reading a 12,000 word manual to figure out how to use a password manager.

Just for fun, I printed the gargantuan "manual" page to a PDF. It's a single page that's 49 pages long when printed. That's what I'm expected to have read just to figure out how to get a password manager to work. That's not a user manual, it's a novella.

I scrolled slowly through the eldritch document's 78 different screenshots to see if there was one of the banner in question, to maybe tip me off where its behavior is documented. If there is one, I could not find it.

I did find the section on the browser integration plugin and read it through carefully, twice. It says nothing about that banner, or how to understand it, or get it to work in a way that seems to make sense. I'll limp along with copying and pasting codes from KeepassXC for TOTP since there's no way I'm going back to Authy or using Google Auth, but for passwords, I've had to go back to the limitations of just using Firefox's built-in password manager. I'd hoped for a better solution than that, but... :-\

Very useful add for me. Works good

The plug-in (the key exchange) does not work for me on Ubuntu 22.04 - although it works well on Windows 11

works for me

If your browser is sandboxed with Snap or Flatpak, this extension does not work. It's not fixable as the required integration breaks the sandbox and so won't be allowed. If you have a browser installed on your host computer (i.e. native, not sandboxed) then there is no problem with this extension. But since Firefox is now ONLY supplied as Flatpak or Snaps on Ubuntu, this effectively locks out all Linux users from using KeepassXC.

> his has nothing to do with the extension itself, but Snap/Flatpak implementation of the browser itself.

But it has everything to do with the extension. It is designed in a way that is simply incompatible with the security model of a sandboxed browser. Nothing about the sandbox is "broken", the kind of code execution required by the extension and the server is what a sandbox is designed to prevent. This is exactly what a malicious extension would do to break out of the sandbox. The team should be working on this, or else users will just abandon the project. I'm certainly not going to try to convince Ubuntu that Snap is broken on your behalf, I'm just going to install something else that works.

Addon doesnt connect to Database - German version - you can click on the buttom but nothing else - no popup, no window on how to connect. I disabled it and went back to native Keepass. Firefox 122.0.1, KeePassXC 2.7.6.

First time reviewer here, and I just want to say that I had a great experience with KeePassXC. I highly recommend it.

It works great, sometimes it forgets the connection to the browser and you have to click the extension in the firefox browser again. Then it will prompt you to name the connection and connect it.
It also worked with adblockers (some forum posts mention that adblockers could potentially block localhost) but it worked fine.