Headless Live Share

[louisabraham]

It has been noted (microsoft/live-share#314) that live share can be used to provide fully remote editing with language server.

I would like to be able to launch a headless VSCode editing session on my server and connect to it through Live Share.

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• live server (#66313)
• not working (#65950)
• Live Share undo affects other users' work in their editors (#66567)

[hickeng]

dup of microsoft/live-share#74

[egamma]

Closing, there now is VS Code Remote.

[hickeng]

Headless liveshare is slightly different IMO.

With remote the developer still has to know all of the details of the remote server and have permissions on it.
With liveshare it's possible for one person to set up the headless server and for many to connect, while knowing nothing but that it's a vscode remote environment.

Think of it this way (and this is something I've wanted for a while) - an option on github repos to "enable liveshare", resulting in a hosted dev environment that is launched on the backend simply by the devs attempt to connect to it, and garbage collected after xxx time without active clients.

• maintainers would be able to get read-only or read-write sessions.
• public would be able to get read-only sessions.
• session per branch.

This is not something I think the vscode remote is ever going to be able to do as the entire approach is inverted.