Native Messaging
Extension → Native Host → QubKey app bridge — macOS and Windows setup.
Native Messaging is the local channel between the browser extension and the QubKey desktop app. Without it, the extension cannot fill your credentials.
Flow: Extension → host manifest com.passmanager.native.json → native process → QubKey IPC → unlocked vault.
Install the host manifest
- Download the macOS extension package from /en/browser-extensions
- Install
com.passmanager.native.jsonin:~/Library/Application Support/Google/Chrome/NativeMessagingHosts/(equivalent folders for Firefox, Edge, Opera) - In the JSON,
pathpoints to the native binary insideQubKey.app - After loading the extension, copy the extension ID shown in the browser into the manifest
allowed_originsfield
- Download the Windows package from /en/browser-extensions
- Install
com.passmanager.native.jsonin:%LOCALAPPDATA%\Google\Chrome\User Data\NativeMessagingHosts\For Firefox:%APPDATA%\Mozilla\NativeMessagingHosts\ path→passmanager-native.exefrom your QubKey install- Copy the extension ID into the host manifest
Verify connection
Launch QubKey and unlock the vault
Settings → Extension — enable Native Messaging if off (settings guide)
Status should show Connected (IPC server active + extension attached)
Test auto-fill on a site saved in the vault
Troubleshooting
Host not found
Check manifest path and that com.passmanager.native.json is valid JSON.
Wrong extension ID
The ID changes if you reload the extension in developer mode — update allowed_origins.
Wrong OS package
macOS and Windows extension builds are not interchangeable.
Next
Full extension install (Chrome, Firefox): Browser extension. Download page: /en/browser-extensions.