Recently every time I open Keepass I get the authorisation screen requesting access for Kee. This happens across different browsers, browsers where the Kee extension is not installed or disabled and indeed even before I open a browser. I cannot figure out what is going on ?
Hi Rocky,
The authorisation window comes from the KeePassRPC plugin. It opens whenever any program connects to its local WebSocket port (default 12546), not only the Kee extension. If it shows up before you even open a browser, something else on your PC is probably trying to connect. Typical candidates are a Kee extension in another browser profile or another Windows user account, or another password tool or “KeePass connector” app. Running netstat -ano | findstr 12546 while the window is open shows which process ID is connecting, and Task Manager tells you which program that is.
Full disclosure, I’m the author: if you’re on Windows and use Edge or Chrome, you could also try KeePassFerry, a fork of Kee/KeePassRPC. It doesn’t open a network port at all. The browser talks to KeePass through a named pipe that only your own Windows account can use, so other programs can’t trigger a pairing request. You pair once with a six-digit code shown in both KeePass and the browser. It can be installed alongside Kee/KeePassRPC.
Thanks for the information. Problem seems to have resolved itself on a reboot.
Regarding KeePassFerry , it looks interesting. However I had a brief look at your Github and it looks like a lot of the code is AI generated (Claude) ?
Glad the reboot fixed it.
Yes, that’s right, and I don’t want to hide it: a large part of KeePassFerry was written with Claude Code (Anthropic’s AI coding tool), and every commit says so. It is not a from-scratch AI project, though. It is a fork of Kee and KeePassRPC, so the core (form detection, filling, the KeePass plugin) is Kee’s long-standing code, and much of the work was changing and removing parts of it.
What I do to keep it trustworthy:
I review and test every change myself before a release.
Users have reviewed it as well. One security review (GitHub issue #9) led to a round of hardening.
The full source is public on GitHub, so anyone can check what it does.
No network port: the browser talks to KeePass only through a named pipe of your own Windows account. The channel is end-to-end encrypted and paired with a code you confirm in KeePass.
Updates are signed: the plugin only installs a new version if the release’s checksum file carries my signature and the setup matches it.
So “AI-assisted, human-reviewed, based on Kee” is the honest summary. If you try it and spot anything odd, I’d appreciate an issue on GitHub.