You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.
Sad to say but I believe that yes it's time to throw in the towel on Bitwarden CLI. They just don't seem to care about it, and it's been broken in various ways for months. Even when it is working, it's too slow (for me) to be very useful. And then you start getting into leaving cached versions of your vault lying around on the disk which probably isn't a great idea security-wise.
I switched to 1Password last week and honestly I can't believe how much better it is, literally in EVERY way. Only wish I had done it sooner, as I've lost days of my life to debugging and working around silly Bitwarden issues.
I didn't make it yet official but I tend to recommend users to use that workflow.
Right now the Masterpassword is visible in cleartext in debug mode - but I hope that will be changed.
1Password is of course very nice and more powerful, specially their global autofill.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
reminds me of #186
I just filed an issue...
bitwarden/clients#9142
Is everyone else having problems too?
The text was updated successfully, but these errors were encountered: