KeePassXC Browser Integration
Where to place the KeePassXC Native Messaging manifest for Misubi Browser and what the manifest should contain on macOS.
KeePassXC Browser Integration
If you use KeePassXC Browser with Misubi Browser on macOS, place the Native Messaging manifest in the Misubi-specific directory.
Manifest location on macOS
Use this exact path:
~/Library/Application Support/Misubi/NativeMessagingHosts/org.keepassxc.keepassxc_browser.json
Manifest example
Create the file with this content:
{
"allowed_origins": [
"chrome-extension://pdffhmdngciaglkoonimfcmckehcpafo/",
"chrome-extension://oboonakemofpalcgghocfoadofidjkkk/"
],
"description": "KeePassXC integration with native messaging support",
"name": "org.keepassxc.keepassxc_browser",
"path": "/Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy",
"type": "stdio"
}
Important checks
- The file name must match the host name exactly:
org.keepassxc.keepassxc_browser.json. - The
pathvalue must point to a validkeepassxc-proxybinary on the machine. - Misubi Browser can still discover fallback manifests from Chromium, Google Chrome, or Brave, which can make troubleshooting confusing if multiple manifests exist.
Recommendation
For Misubi Browser installs, use the Misubi-specific path as the canonical location and avoid relying on fallback manifests from other browsers during debugging.
Last updated on