Command Line Interface / CLI
1Password has a very nice CLI for use in the shell that would be a great feature for you to support, too.

-
Jean-Yves CAMIER commented
I need CLI to switch from 1password to proton pass
-
Daniel commented
Critical requirement here, too.
-
Lukas Hahn commented
This is the last thing keeping me from using Proton over 1Password.
-
Dave commented
This is a critical requirement for my use cases. The main reason to stick to 1Password are:
- CLI for using secrets on scripts
- Integrated SSH Key Agent
- Support / Generate SSH keys -
Raymond commented
Only thing keeping me on 1password is 1Password CLI for adding easy, secure authorization coded into scripts. I don't even use it for ssh auth anymore ("secretive" is great).
-
Yes, please add this! Top priority!
-
Ozh commented
At least, if not a full blown CLI, command line options would be cool (like, start the windows or linux app with --export --format json)
-
aibix0001 commented
I am looking into Proton Pass to substitute 1Password. Unfortunately, since I rely heavily on their CLI tool and its plugin eco system, this is a non-option right now. Looking forward to seeing those features!
-
Timo commented
Having a CLI would be great. Especially for pulling secrets in the terminal. But would also enable other features like integrating it into Raycast.
-
Michael Rolli commented
Coming from 1password and using op command quite a lot. SSH-Agent support and pulling secrets from the CLI is a deal breaker for me. As soon as this is available, we would become family plan members for sure.
-
Diego Navarro commented
That would be amazing to integrate to enterprise apps.
-
Felix Leitl commented
I want to migrate from 1Password to Proton Pass, because my free trial as a student expires, but the CLI is critical to me, as a computer engineer. Especially the ssh agent
-
Ronald commented
Ideally the desktop app would do autotype like keepass does. Next best is a cli so I can make autotype myself using AppleScript. Without this I will have to stick with Bitwarden.
-
Mistral commented
Proton product are mainly use by tech savvy people. A CLI i a good way to integrate with power user workflow, company and can pave the way for business need that can be answer by Proton.
The more people and power user can integrate with proton, the better it is. -
No, YOUR Name commented
+1 for CLI on Proton Pass, sadly my personal workflow slowed a little bit but the hidemyemail is too great and I don't really like having multiple apps at the same time as I know this is just a temporary sacrifice
-
Aaron Brock ☂️ commented
I'm in the same boat as many on this thread ~ this is what's holding me back from adopting proton pass officially.
-
Lance Stephens commented
Have proton pass by virtue of proton vpn. Would like to migrate .env files to pass but lacking a cli means I'll probably stick with bitwarden for programmatic access of secrets.
-
shaunwallace commented
I agree that in order to make Proton pass viable for me, I really need to have a cli command like `op` that allows me to fetch credentials. I use this specifically for authenticating with Okta / AWS and Kubernetes for work.
-
ZSH commented
Would be super useful in a lot of power user scenarios on both linux and macos
-
Julz commented
I am already using ProtonPass, but as someone who does remoting into different machines I have alot of username/password/mfa combos and it would make my work WAY easier if I could access those in my shell.