rbw VS rubywarden

Yes, but it is quite uncomfortable to use, requiring you to get a session key and storing it somewhere. Instead, I've had good experiences with [rbw]. Maybe that would also be interesting for GP.

I've used to rbw for a rofi (and rofi-like frontend): https://github.com/fdw/rofi-rbw/

[rbw]: https://github.com/doy/rbw/

See https://github.com/doy/rbw for all the details

You can try using rbw to do that.

If you'd like a CLI client (also written in Rust), I'd recommend rbw, it's really simple but works a lot better for me than the official client.

If you know rust and C#, you can also look at bitwarden/server implementation (C#), or dani-garcia/vaultwarden (rust). Lastly, doy/rbw is a fully fledged CLI implementation of a client, and there is always looking at the official client implementation (bitwarden/browser and bitwarden/cli).

However, I've moved from that to rbw and I can honestly say it's much better. It handles locking/unlocking very well, and the interface actually makes sense.

I agree that the Bitwarden cli is awful. You have to log in, and store the token it gives you manually so that it knows you're logged in.

However, I found https://github.com/doy/rbw , and alternative OSS cli written in Rust, and it's exactly what I wanted. (Disclaimer: I liked it so much I wrote a rofi integration for it.)

You can! I actually started implementing something for the CLI but never got to finish it. Most of the information I got was from this article, which is how rubywarden (now discontinued) was implemented.

The official self hosted server required MS SQL and thus a lot of RAM that I just didn't have in my home server. There was popular server implementation that was written in Ruby, but that didn't have the password sharing functionality implemented. I wrote enough Ruby before to know I didn't want to write that functionality myself.