VaultPilot Browser Vault Extension gives paired devices access to vault records through user-action autofill, save-login prompts, update-login prompts, and active-site record-count badges.
Installing the extension grants no access; each device must be paired and approved in VaultPilot. Treat pairing codes as short-lived authorization material, give approved devices clear names, and revoke any device no longer controlled by its intended user.
Install from Chrome Web Store
Chrome Web Store listing:
https://chromewebstore.google.com/detail/vaultpilot-browser-vault/hjkbedlaieikhkoplgpiohlaakgebobi
The extension ID is hjkbedlaieikhkoplgpiohlaakgebobi.
For managed fleets, deploy that extension ID through Chrome or Edge policy. Chrome updates the extension from the Web Store automatically. The extension About view can ask for an update check, but the browser decides when an available update is applied.
The release ZIP is an emergency fallback only; do not use it as the normal installation path.
Pairing flow
- Install VaultPilot Browser Vault Extension from the Chrome Web Store.
- Open the extension popup.
- Enter the VaultPilot server address.
- Enter username, device name and extension PIN.
- The extension creates a short-lived pairing code.
- Approve the device in VaultPilot: Browser extension.
- After approval, the extension can open the vaults that user is allowed to use.
User experience
| Feature | Behavior |
|---|---|
| Badge count | The extension icon shows the number of matching records for the current site. |
| Autofill | User action fills the selected record into the current page. |
| Save login | New login detection can prompt the user to save a new record. |
| Update login | Changed username/password detection can prompt the user to update an existing record. |
| Notifications | Pairing, revocation, autofill and save/update states are shown in the popup and browser notification surface where supported. |
Security model
- Extension private material is protected by the extension PIN and browser profile storage.
- Persistent extension storage does not contain plaintext secrets.
- Records stay encrypted in the extension until the user acts.
- Plaintext is decrypted only in the active extension session after user action.
- Lost or untrusted devices should be revoked from the VaultPilot panel.
Operations checklist
- Pair only named devices.
- Use the Chrome Web Store listing for user installs and updates.
- For managed fleets, distribute the extension ID through browser policy.
- Review the Browser extension screen after updates.
- Revoke devices that are unused, unknown or no longer compliant.