July 7, 2022 by Brigit Murtaugh, @BrigitMurtaugh
A remote present and future
In 2019, we released the Remote Development extensions, which let you use VS Code locally to develop applications “remotely” on the Windows Subsystem for Linux (WSL), in Docker containers, and on remote physical or virtual machines you manage over SSH. In 2020, we took another step forward with remote development with GitHub Codespaces, which let you use VS Code locally or in a browser to develop applications on a remote virtual machine that is hosted and managed in the cloud for you.
We can do this because VS Code is, by design, a multi-process application. Conceptually, the front end (where you type your code) runs in one process and a backend service (which hosts extensions, the terminal, debugging, etc.) runs in a separate process.
Today we are releasing a private preview of the backend service that makes this all possible, the “VS Code Server,” along with a CLI that makes it easy to install, update, manage, and connect to the service. You can install the server wherever you like (a local development machine, a VM in the cloud, etc.) and access it securely through the browser using VS Code for the Web (also known as vscode.dev), without the hassle of setting up SSH or https (although you can do that if you want as well 😊).
As the service that you use to securely connect to the VS Code Server is in private preview, you’ll need to request access through a signup form. You’ll receive an email, hopefully only within a few weeks, once you can start using the service.
At that point, here are step-by-step instructions to quickly get up and running:
- Install the VS Code Server on your remote machine (or wherever you want to develop against).
Note: There are different install commands for different remote architectures, which you can review in the server documentation. This post will set up the VS Code Server in a Windows Subsystem for Linux (WSL) instance, which provides a true, isolated Linux environment on Windows and can server as our “remote,” isolated machine.
Run the following command in a WSL terminal:
wget -O- https://aka.ms/install-vscode-server/setup.sh | sh
- Start the VS Code Server by running the following command in your WSL terminal:
code-server -hto see all the available commands to launch and manage the server.
- Your WSL distro will communicate with vscode.dev through a secure tunnel, which allows you to connect to your computer from vscode.dev, no matter what network you’re on.
You’ll be provided a device code and URL to authenticate your GitHub account into the VS Code Server’s secure tunneling service.
Authenticate into the tunneling service by entering the device code at the provided auth URL.
- If this is your first time launching the VS Code Server from this WSL instance, you’ll be prompted to enter a name for your connection. The CLI will suggest a fun default “adjective-noun” name (examples shown below), which you can choose to accept too.
- After authenticating and providing a machine name, the CLI spins up a server instance and generates a vscode.dev URL. To connect to your WSL instance, you can open this URL on any device.
Note: You can also connect to your WSL instance directly from vscode.dev: Open the command palette (
F1) in vscode.dev and run the command Remote Server: Connect to Remote.
Congratulations, you’ve successfully installed and run the VS Code Server! The connection is fully established once you visit the generated vscode.dev link. Your WSL distro’s files should be present in the VS Code Explorer, and you can start coding against it from vscode.dev.
A preview of a larger journey
The VS Code Server is currently a private preview. In this early preview, the
code-server CLI is distinct from the
code CLI you use today to launch the desktop VS Code, to install extensions, and more (run
code -h from the terminal 😊). This is just the first step along the path towards a fully unified
code CLI that lets you manage both the desktop and the server.
We’re excited for you to try out the VS Code Server. You can learn more about it, including the architecture, other commands, implementation details, and scenarios, in its documentation and intro video. If you have any issues or feedback, please file an issue in the VS Code Remote Development GitHub repo, and you can Tweet us your thoughts @code.
Brigit Murtaugh, @BrigitMurtaugh