I think just pressing a hotkey to auto-type the correct password and username based on the currently active web page, program, window, etc. is easier still than opening a terminal and running a command. To me at least.
Well, I always have guake running, so for me doing it all on the command-line is WAY faster and more convenient. I forgot to mention that "pass" also has command line completion - which makes retrieval trivial.
I would also be surprised if someone somewhere hasn't already written an "autotype" layer over pass, but thats not something I am personally interested in.
I do agree that for end users this may not be the case. For non-technical people (my parents, for example), I mostly recommend writing their passwords down on paper. They have very few passwords as-it-is, and almost none of them are critical.
My own use case, where I have literally hundreds of pieces of info I need to secure (passwords, key-files, gpg keys, ssh keys, etc), is very different from that of such users. Hence different tools.
Oh, also, "pass" can copy the password to the clipboard, making the copy-paste scenario trivial. In fact, it goes even further by clearing the pass from the clipboard after a preset time.
KeePass can copy to clipboard or do autotype. And I'd say every password manager has to make sure to clear the clipboard afterwards in such cases. This is basic and bog-standard functionality which was present in every password manager I used so far.
Unfortunately, that's useless if you need to store passwords for anything other than web use, if you need to automate the entering of passwords and so on.
I routinely use it for entering passwords to SSH or RDP sessions, and various other non-web passwords. Why would auto-type work only on the web anyway? You can also customise how the password is entered depending on where you invoke auto-type, e.g. if you need username/password, separated with a tab key in one place, but only the password in another.
