Please note
Items on the roadmap indicate development initiatives rather than delivery date. We strive for transparency and will update this roadmap as a living document. You can also review previous release notes at any time.
Before posting a new feature request, please start here
Community Code Contributions
If you are a community developer passionate about working on a specific feature request, find out how to get started.
Hey @viktor Bitwarden send functionality will be expanded so that you’ll be able to send a vault item and have someone add it to their own vault, including those outside of the organization.
I understand and share your concerns. When you mention “Research and Development,” it can seem quite broad and may be hard for users like myself to grasp exactly what that encompasses. It could imply these features might be implemented in 1 year, 5 years, or even 10 years. The ambiguity makes it challenging to set expectations. Therefore, it would be highly beneficial if you could be more transparent about your planned improvements and the timelines. While I completely appreciate the importance of security, I believe that clear and frequent communication with your users is just as vital. This can help us feel more informed and valued as members of your user base.
Hello dear Bitwarden, first of all thank you for the fantastic job you do, we really appreciate it. just like everyone else, I wonder when we will know more detail about the roadmap? time has passed and we have no info. Can you share something? once again grateful for your efforts and grateful for answers.
I’m confused. Does that mean none of the features on this Roadmap 2023 are planned to release in 2023? They are just some features possibly “beginning research and development” in the first half of 2023 and some to be considered sometime after 2023 (“Future initiatives”)?
Is there a roadmap for features that are actually planned to release in 2023?
I’m here for the security and commitment to independence, not the new features. Those are nice, and they’ll come when they’re ready. Anxiety over when new features will be here is the equivalent of keeping up with the Joneses. Unless of course you have a business requirement depending on one of those upcoming features, in which case you should be asking the support and sales teams, not badgering on a public forum.
Frankly, I appreciate the fact that they’re not kowtowing to incessant pressure on updating a public roadmap they have no obligation to produce. This kind of pressure could impact feature release, weakening secure development. Sure, the communication could be better, but I’m pretty astonished at some of these comments.
Hi - Gina from the product team. The latest update of the roadmap is aimed towards providing more transparency about what items are in active development and what items are next in the queue or working through additional research. As the Bitwarden team releases new features, the roadmap will continually get updated so that the Bitwarden community will know what items are likely to be released near-term.
We do read and appreciate all the feedback. As transparency is a core value for Bitwarden, we will continue to improve on providing more updates to our supportive community.
Are there plans to add PRF WebAuthn extension support to passwordless.dev? Since it’s supported in the core Bitwarden product, I’m hoping it’ll be rolled out to the passwordless API soon.
Hey @san4d, Anders here and I lead the work on Passwordless.dev.
I’m interested to learn more about your use case for PRF. It’s not high up on our roadmap, mostly because it’s not something we’ve seen a lot of interest in, and secondly because PRF still lacks some platform-support.
With that said, I’d love to hear your use case, if you can share?
I’m a current Passwordless.dev user gearing up for a product launch. I’m using passkeys as my primary authentication method. Part of my roadmap involves storing sensitive financial documents. I’d love to be able to use passkeys as part of an end-to-end encryption strategy for those documents. It’s the classic client-side encryption use case.
It’s a shame certain platforms haven’t adopted it yet. I understand why the lack of support would impact it’s position on your roadmap. Happy to chat more over email if you’d like.
Interesting use-case. While enabling PRF support is possible to build, for e2e encryption you probably have other needs that you’d like a product/sdk to solve, like supporting multiple keys, key rotation and recovery etc which is a bigger piece of work than just enabling prf. Do you share that view?
Those features would certainly be useful. A little more about my use case: I already support multiple passkeys and the files I mentioned may be shared with other identities in the account.
If I only had PRF, the plan would be to use the resulting key as a seed to generate a private/public key pair using another scheme. I’d create a separate, symmetric key when the account is created to by shared later and persist the public key and encrypted account key (using the corresponding private key). To share that symmetric key to other people in the account or other passkeys associated with the identity, I’d get the encrypted account key, decrypt the key in the browser, then encrypt it again using the target’s public key.
Disclaimer: I’m a few months away from needing to implement this. The above is a rough draft, and I haven’t thought through all the edge cases. I’m in the discovery phase. Just sharing to provide a bit more context.
first of all thank you for the fantastic job you do, we really appreciate it. 
just like everyone else, I wonder when we will know more detail about the roadmap? time has passed and we have no info. Can you share something? once again grateful for your efforts and grateful for answers.
