I’ll update this post as time goes on, and I find more things are suboptimal.
I’ve been waiting quite a long time for Bitwarden to enable the ssh-agent, and now that I can use it, I find that there are a few points that cause me friction, working with it on a day-to-day basis.
I’m on Linux (NixOS), and I use ssh keys for all things git related, so on a busy day, literally hundreds of times. Here are the points that aren’t that great so far:
Re-minimize (/ close) Bitwarden
If Bitwarden was minimized, either to the drawer or to the tray, it should return to that state, and thus re-focus the app I was previously working in.
Quicker authorization
I would prefer it, if the “Authorize” button would have initial focus, instead of the “X” for closing the popup inside Bitwarden. Currently, I have to hit Tab + Enter, instead of just enter, which is a bit inconvenient.
If this is not desirable, due to the possibility of accidental confirmations, maybe add alt + a (authorize) / d (deny) shortcuts to such prompts?
Cache the authorization of keys
Git clients often make multiple requests to generate their result(s). So I often have to approve 3 or more prompts, just so I can start committing.
Even without a git client, I make multiple requests, when committing. At least one git pull, followed by the eventual git commit (this obviously doesn’t normally make a request) and git push
I would find it useful when the key stays available for some time, e.g.: 5 minutes.
Furthermore, it would be worth considering allowing unrestricted access to the SSH-key, once it has been authorized. Many git clients can be configured (or are set up by default), to do periodic fetches, to inform the user about potential updates on the remote.
