

For instance, on Windows the manifests are located at C:\Users\\AppData\Roaming\Bitwarden\browsers and on macOS these are in Application Support for various browsers ( for example). Manifests are located in the browser subdirectory of the Bitwarden configuration directory. To enable communication between the desktop application and development versions of browser extensions, add the development IDs to the allowed_extensions section of the corresponding manifests. When you enable browser integration in the desktop application, the application generates manifests which contain the production IDs of the browser extensions. Out of the box, the desktop application can only communicate with the production browser extension. Native Messaging (communication between the desktop application and browser extension) works by having the browser start a lightweight proxy baked into our desktop application.

You can now load the extension into your browser through the browser's extension tools page:
