I don't do a lot of "serious stuff" on my phone, so whenever I need to input a password there I just display the password on my computer and enter in there, if I regularly needed to access my passwords however my current solution would be unusable.

As for my workflow I don't have any auto-fill on my browser, I just use "pass -c my-password-entry" to put it in the clipboard and paste it from there. It's arguably less secure than having it autofilled I suppose, but it hasn't been an issue so far (and pass clears the clipboard after 45 seconds to mitigate the risk).

Then I have a bunch of scripts for starting my VPN connections, my email client etc...

I should add that my pass's GPG key is stored on a yubikey and I need to physically press the button to decrypt, so that adds a pretty good layer of protection.

So yeah, I realize that my use case is incredibly niche, but I do think that being able to use your password manager in scripts could be useful in some cases even for people who are less enamored with the terminal than I am.

For me I have 1 use case - logging onto a Cisco Anyconnect VPN.

Since I do this multiple times per day I wrote a simple bash script that invokes Anyconnect and supplies the VPN credentials it pulls out of my password manager. I alias this script in my shell environment so it's as simple as typing "vpn" to get logged onto the corp network, saving the hassle of mousing around to get onto the VPN.

I use it fairly regularly for cases where I want to input something sensitive on the command line, and not have that stored in my bash history.

For example something like

curl -u user:"$(pass SomeSecret)" https://api.website.com

> I use it fairly regularly for cases where I want to input something sensitive on the command line, and not have that stored in my bash history.

Nice usage.

You could also use HISTIGNORE variable, history -d, or unset HISTFILE. Here are some examples [1]

[1] https://www.rootusers.com/17-bash-history-command-examples-i...