Right now I can access 1Password on my WSL Debian installation using the CLI. But I have to enter my master password even when Windows is authenticated. I was just curious if it's possible to connect the two (a-la the SSH agent forwarding magic outlined here - https://1password.community/discussion/128023/ssh-agent-on-windows-subsystem-for-linux) 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided Browser:_ Not Provided

I have a solution for Windows 11 WSL2! Please let other people know if this solution does not work for you. 1. Open CMD and "winget install 1password-cli" or go to 1password docs and figure out how to install the WINDOWS version of 1password cli. 2. If you installed with winget, you should be able to navigate to "C:\Users<username>\AppData\Local\Microsoft\WinGet\Packages<1password_cli_package_id>\op.exe" 3. if you did not use winget, navigate to the executable of the cli program 4. add this to your ~/.bashrc file in wsl: alias op="/mnt/c/Users/........./op.exe" Magic!

One thing to be aware of if invoking the Windows op.exe from WSL: environment variables are not passed by default to Windows processes spawned from WSL (& vice versa). Some tools that integrate with the 1Password CLI rely on passing environment variables, e.g. OP_FORMAT, which will result in issues if the tool is run from WSL. In particular the https://developer.1password.com/docs/terraform/ (in one configuration) wraps the CLI, and relies on environment variables like OP_FORMAT=json to configure it to give output that it can parse correctly. When running Terraform in WSL against a Windows CLI, these environment variables don't get passed to the spawned process, which means amongst other things that the CLI output is not JSON as the Terraform provider is expecting which causes things to fail with an error message like: "Unable to read vault, got error: invalid character 'I' looking for beginning of value". Once I'd realised the cause of the issue, my workaround was to wrap the op.exe binary with a shell script that directs WSL to forward all OP_* environment variables to Windows using the https://devblogs.microsoft.com/commandline/share-environment-vars-between-wsl-and-windows/ environment variable. My op script sits next to op.exe and looks like: ```bash !/usr/bin/env bash mapfile -d '' op_env_vars < <(env -0 | grep -z ^OP_ | cut -z -d= -f1) export WSLENV="${WSLENV:-}:$(IFS=:; echo "${op_env_vars}")" exec op.exe "$@" ``` This solved my issue and I wanted to share in case anyone else is in the same situation, and to ask that this use case is considered if/when an official solution is implemented or documented!

Hi anishlr: There currently isn't any way of connecting 1Password CLI running in Windows Subsystem for Linux to 1Password for Windows running on the host. With that said, it's something I'd love to see too, so I'll share your feedback on an internal discussion we have about this. While I can't promise anything specifically, we use feedback like yours to help inform the future of 1Password. Jack ref: IDEA-I-1662

Just to add to the list of people, that is something I wish for as well.

This would be huge. I have currently adopted @matfax's solution, which works. I haven't used any CLI plugins yet. But generally, I think having a turnkey solution for WSL would be really useful.

Is it possible for 1Password CLI running on WSL to connect with 1Password hosted on Windows?

41 Replies

dmbuil
Occasional Contributor
2 years ago
Definitely a +1
acjay
New Contributor
2 years ago
This would be huge. I have currently adopted @matfax's solution, which works. I haven't used any CLI plugins yet. But generally, I think having a turnkey solution for WSL would be really useful.
btmurrell
Occasional Contributor
2 years ago
bump. +1 for me. we all expect this to "just work". for me, the ability to have a real shell vis a vi WSL is the only reason this programmer is using Windows. To my understanding, there's a pipeline btwn the WSL environment and Windows (be it ports or binary compatibility), but having op cli available in WSL, connecting to the Windows 1p app is a critical piece.
Former Member
2 years ago
has there been any progress since then? has any kind of roadmap been prepared?

it would be very nice to be able to use the 1password CLI via WSL2, especially the shell plugins
Former Member
2 years ago
I also would love to see this released ! Windows co-workers wait for this !
Former Member
2 years ago
What I found is that it works if you create a symlink in your WSL machine, pointing to op.exe on your Windows host:
ln -s /mnt/c/Users/user/AppData/Local/Microsoft/WinGet/Links/op.exe /home/user/.local/bin/op

It works with other Linux commands (in opposite to alias), and in particular with ansible.
Former Member
2 years ago
+1
Former Member
3 years ago
+1
Stanzilla
Occasional Contributor
3 years ago
Would love to see this as well
Former Member
3 years ago
Thank you everyone for chiming in!

We'll let you know once we have more details here.

Forum Discussion

Is it possible for 1Password CLI running on WSL to connect with 1Password hosted on Windows?

41 Replies

Recent Discussions

macOS 26 beta browser extension very slow to open

`op account add` with `Integrate with 1Password CLI`

Console flooded with errors when clicking links during 1Password passkey selection dialog

WSL2 Arm Build

1password doesn't seem to remember the key approval for JetBrains IDEA Ultimate