Beta advisory : Betas do not feature production level quality or testing. We advise you to use a separate and dedicated Bitwarden account for testing when running beta builds to make sure you do not suffer any data-loss. More detail here.
If you encounter bugs in the beta builds, please report them on GitHub for the team to review.
Thanks. Will I need to delete these beta builds and go back to the standard build once the tests are over? I was burned by how you tested the new extension. I had assumed it would keep getting updated even after the beta ended, but nope, it just became an unmaintained the security risk and I had to redownload the old extension again.
I’m curious about this feature, and would potentially like to participate in beta testing, but I would appreciate if you (or @andersaberg) could clarify the following:
What exactly does the Bitwarden-Beta-2025.10.2-x64.appx artefact install? Is it a beta version of the Bitwarden Desktop app, or is it some kind of background layer that facilitates communication between the OS and the Desktop app (and if the latter, is it compatible with the portable Desktop app)?
If one wants to no longer participate in the beta testing, what is the procedure for doing a clean uninstall of everything that has been installed or modified by Bitwarden-Beta-2025.10.2-x64.appx?
The Github PR includes the following warning: “We advise you to use a separate and dedicated Bitwarden account for testing when running beta builds to make sure you do not suffer any data-loss.” — what type of “data-loss” could occur if installing this beta build. Also, how do we prevent our main Bitwarden account from being affected by bugs in the beta build (i.e., should we only install this on a dedicated device where we never log in to our main Bitwarden account?)?
I also would like to read a more comprehensive answer to that – but the blog article update @dwbit linked suggests, it’s indeed a Beta version of the desktop app, if I interpret this correctly:
In this beta release, the feature requires installing the desktop application from the Github repository. It will later be widely available through the standard desktop application install.
And if that would be the correct interpretation, then I would guess, it can be deinstalled as easy as any version of the BW desktop app.
We’re excited to ship this beta, but this is not a production grade release. Let me be as transparent as possible.
What exactly does the Bitwarden-Beta-2025.10.2-x64.appx artefact install? Is it a beta version of the Bitwarden Desktop app
It installs a separate application on your computer, named “Bitwarden Beta”. If you don’t want that Beta version on your machine anymore, you should be able to uninstall it as normal
However, since this is a Beta version that is built straight from our development branch (PR) it has not gone through our QA process and is being built automatically from code that is being pushed in active development. There are no guarantees that things will uninstall cleanly.
what type of “data-loss” could occur if installing this beta build.
Again, this code has not gone through quality testing. We may include code that logs sensitive information to logfiles on your system, or we may write code that ends up corrupting data in the vault. While that normally doesn’t happen - this beta does not come with the guardrails and guarntees our official releases does.
Can it be installed alongside an official Desktop app release (e.g., in my case, a portable Desktop) — i.e., if we use our main Bitwarden account only on an official production release of the Desktop app, can we be assured that the data in this main Bitwarden account will not be at risk from corruption if we simultaneously use the “Bitwarden Beta” app with a test account?
Just tried out the beta version, everything works well except for this:
When I tried to enable the browser integration as usual, I got the message: “Unfortunately browser integration is currently not supported in the Microsoft Store version.”
This seems to be an old issue:
However, according to Microsoft, only a packaged app can act as a plugin passkey manager.
So here’s my question: do we have to choose between native passkey support and browser integration, or will the browser integration issue for packaged apps be solved later?
PS: I know there’s another workaround: the “unlock with passkey” feature for the browser extension is coming soon, but it requires PRF passkeys, which means only a limited number of users will be able to use it.
I noticed that if you try to launch the beta version while the official desktop release is running, it opens the stable version instead, preventing the beta from potentially corrupting the data.
I would also like an update about this project, and when there will be new beta’s (or a release)? The 1Password implementation is up and running since november 2025, in general production.