No, and don't expect it or Live Share to ever land[0].
None of the "Remote" extensions are FOSS, and they restrict usage to "validly licensed" copies of VS Code[1] – plus the server side code for it is closed source. So getting it into Codium would require a clean room implementation, essentially.
The extension API proposals and RPC protocol are open sourced and the server code is just an electron-less version of the regular VSCode extension host (hence, remote extension host, REH). This is all part of the VSCode OSS release.
What the proprietary extensions provide is integration. For example, the SSH variant automatically installs and launches an REH instance on the remote host and sets up port forwarding. If you are willing to start the instance and to forward ports yourself, you can use the tiny extension I wrote [1,2] (See the README how to enable the necessary extension proposals.). It allows you to connect to a local port you configure in the config. It is based on an example extension (vscode-test-resolver) in the OSS release that is used to test this functionality [3].
Microsoft is not really hiding any of this, so I am a little surprised, that nobody wrote a similar extension so far...
Nice work! The Remote Development license I linked earlier specifically excludes one from "reverse engineer[ing]" the code – which appears also to apply "to any Microsoft services... for the software".
IANAL, but I'd definitely be nervous to touch this stuff with a 10ft pole.
As a person who administers servers I absolutely HATE that vscode does this.
I don't know much about the specifics of remote deployment, but I feel like having vscode do this is just the wrong approach. I would say it probably needs to be some other CI/CD pipeline or something outside of the editor.
The problems I have is that every user gets like 1.5G of node junk stuffed in their home directory to support this. VScode spawns processes as the user that can't be controlled that can just kill servers (This is one bug I found, but there are issues with this that go much farther back than 2 years ago, https://github.com/microsoft/vscode-remote-release/issues/26...)
There doesn't seem to be any way to control this on the server side, so if I have users with the ability to write to their home directory, I cannot stop them from pushing this and potentially killing an instance.
