I’m also doing WSL-centric development and I’m not even really gaming on that machine, I just appreciate the comforts that come with competent multi monitor support and reliable wake from sleep.

My biggest frustration with WSL at present is that 1Password won’t properly support proxying their ssh agent into it. (Though in googling it again just now, I see a suggestion to try something called npiperelay, so I’ll spend some time seeing again if I can get that working)

▲

Cu3PO42 3 days ago | parent | next [-]

I can confirm npiperelay does the job just fine.

If you happen to use Nix, I have a quick and easy package at github:Cu3PO42/gleaming-glacier/next#wsl-ssh-agent. Simply install that and 'source $(which wsl-ssh-agent)' in your bashrc and you should be good to go. (There's also a HM module in the Flake.)

▲

ycombinatrix 3 days ago | parent | prev | next [-]

You can actually run the windows ssh.exe binary directly from WSL, no extra setup needed. Give it a try.

	▲	mikepurvis 3 days ago \| parent \| next [-]
		I’m aware that 1P themselves recommend this but I don’t like it; a lot of my usage is other things like git or docker or ansible calling ssh and I don’t want to deal with those things having to also be steered to an alternative ssh implementation.
	▲	xzez 3 days ago \| parent \| prev [-]
		I used to use the `npiperelay` method but have since switched to this and it works nicely.

▲

olivermuty 3 days ago | parent | prev [-]

No such thing needez, just alias ssh to ssh.exe and ssh-add to ssh-add.exe and it works out of the box.

	▲	issei 3 days ago \| parent [-]
		aliasing the ssh.exe generally works, but not for all applications. I had issues with this approach while running ansible playbooks ("getsockname failed: Not a socket").