We’ve been working on a v2 of the Bitwarden SSH agent and wanted to share a quick heads-up on what to expect.
The core goal of v2 is maintainability. It’s an under-the-hood rebuild that lets us fix bugs faster, improve test coverage, and finally act on some long-requested features. The UX isn’t changing.
A couple things worth noting:
Development is now fully focused on v2, with v1 only receiving security patches and regression fixes going forward.
All new development is moving to v2, which is where bug fixes and new features will happen.
We’re revising the Help Center to make clearer what’s supported and what isn’t.
More details to come. Happy to answer questions in the meantime!
Will it support adding non-Bitwarden ssh keys (using ssh-add or similar)
Will the issues with account switching be fixed?
Will we gain the ability to import/create SSH keys in the web vault?
Will it support SSH certificates?
All that being said, the major operating systems these days all include fully functional SSH agents, and Pageant is an easy install. I’m of the opinion you should just implement an agent to add keys stored in Bitwarden to an existing agent rather than reinvent the wheel.
Hi there, and thanks for the feedback! V2 won’t be launching with any new features, but will be where we fix bugs and review existing feature requests.
Hey Peli, this communication is primarily aimed at those who were submitting PRs to the V1 agent, feel free share any info you want passed along to the team.