Managed to set up cross-platform #Rust development environment with @zed using Windows as a remote host. Some tips:

* You have to let Zed proxy through the Windows firewall (I just disabled it as usual, since this is a lab network)
* The default cmd.exe shell doesn't seem to work with remote tasks (I suspect character escaping error), you have to explicitly set powershell.exe

I was initially concerned about usual Windows SSH shenanigans, but surprisingly my config (with jumphost and an agent) worked flawlessly from Linux.

h/t @raptor for the tip!

Now I'm in a nasty rabbit hole, because the Zed server doesn't seem to use /TCP/UDP connections, yet it is somehow affected by the firewall...

"The windows firewall can block named pipes even when they are only used for inter-process communication on the same machine." - OK this may be related. Also, WTF?

Source:
https://superuser.com/questions/462443/what-are-reasons-for-local-windows-named-pipes-to-fail