source for planned integration: https://issuetracker.google.com/issues/392521081?utm_source=...
source for planned integration: https://issuetracker.google.com/issues/392521081?utm_source=...
So the development wasn't local, but it was sort-of usable. (And the editing is local in any case.)
So you start the 'server' on eg your desktop, and that registers with eg GitHub or Microsoft (or perhaps another service, not sure how open the system is), and then you can use any other computer to connect to your system via GitHub or Microsoft (as a proxy, I think). The other computer can either run just a browser, or can run a vscode (which is basically also a browser in the end).
See https://code.visualstudio.com/docs/remote/tunnels
Yes, the nice thing about the tunnels is that the computer you want to develop on doesn't have to be reachable from the internet. It only has to be able to reach the internet. GitHub (or Microsoft) play the man-in-the-middle.
It's really convenient. I often use it to develop from my laptop on my desktop, even when they are on the same local network: because it's basically just as fast, but I don't have to worry about which network I'm on, it just always works (as long as I have Internet access on both machines. But if that ever stops, I'm not really going to develop much anyway.)