Undoubtedly, these are great features, but what about everything else? If I have firefox open and run ps aux | grep -i keepassxc-proxy I can see the binary running, however it does not happen when only Brave is running.KeePassXC is an open-source, offline password manager, that is also free. So I believe the problem is that keepassxc-proxy is not launched by Brave? And also have the socket file /run/user/1001/app// The file /run/user/1001/ is a symbolic link to itself, what is correct.

The Unix Domain socket path check also seems correct.

I believe because the command pgrep brave returns multiple PIDs (while firefox only returns one PID) Sudo strace -f -p $(pgrep brave) 2>&1 | grep keepass When I try monitoring the process with Brave

The keepassxc-proxy binary is not running, and I can not run it manually.

'description': 'KeePassXC integration with native messaging support', 'chrome-extension://oboonakemofpalcgghocfoadofidjkkk/' 'chrome-extension://pdffhmdngciaglkoonimfcmckehcpafo/', ~/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/_browser.json The path for the native message script for Brave browser is not indicated. I followed these guidelines to track the problem. It should ask for a new association key when pressing connect and connect to the database KeepassXC-Browser should connect to KeepassXC Database.

KeepassXC-Browser can not connect to the KeepassXC Database.

Open the KeepasXC aplication and database (all well configured, and Browser Integration with Brave activated).The problem does not happen when Brave stable release (v1.45.131 ) is used. KeepassXC-Browser does not connect to KeepassXC when Brave Beta is used.

Keepassxc chromium