Visual Studio Code Server
The Visual Studio Code Server is a service you can run on a remote development machine, like your desktop PC or a virtual machine (VM). It allows you to securely connect to that remote machine from anywhere through a local VS Code client, without the requirement of SSH.
What is the VS Code Server?
In VS Code, we want users to seamlessly leverage the environments that make them the most productive. The VS Code Remote Development extensions allow you to work in the Windows Subsystem for Linux (WSL), remote machines via SSH, and dev containers directly from VS Code. These extensions install a server on the remote environment, allowing local VS Code to smoothly interact with remote source code and runtimes.
We now provide a standalone "VS Code Server," which is a service built off the same underlying server used by the remote extensions, plus some additional functionality, like an interactive CLI and facilitating secure connections to vscode.dev.
Architecture
We want to provide a unified VS Code experience no matter how you use the editor, whether it's local or remote, in the desktop or in the browser.
Access to the VS Code Server is built in to the existing code CLI.
The CLI establishes a tunnel between a VS Code client and your remote machine. Tunneling securely transmits data from one network to another.
The VS Code Server experience includes a few components:
- The VS Code Server: Backend server that makes VS Code remote experiences possible.
- Remote - Tunnels extension: Automatically loaded in your local VS Code client, it facilitates the connection to the remote machine.
Scenarios
The VS Code Server allows you to use VS Code in new ways, such as:
- Developing on a remote machine where SSH support may be limited, or you need web-based access.
- Developing on a machine that doesn't support the installation of VS Code desktop, such as an iPad / tablet or Chromebook.
- Experiencing the client-side security benefit that all code can be executed in the browser sandbox.
Getting Started
You can choose from two paths to enable tunneling, which are described in greater details in their respective docs content:
Things to try
Licensing and other commands
Upon first run of the VS Code Server, you'll be prompted with the terms of the license. You can view the license for the VS Code Server here.
* Visual Studio Code Server
*
* By using the software, you agree to
* the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and
* the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).
You can explore the CLI's other commands by running code -h, and specifically the tunneling commands by running code tunnel -help:
Extension commands
As with the CLI, the VS Code Remote Tunnels extension has additional commands you can explore by opening the Command Palette (F1) in VS Code and typing Remote Tunnels. You may learn more in the Remote Tunnels documentation.
Telemetry
If you want to disable telemetry, you can pass in --disable-telemetry when launching the VS Code Server: code tunnel --disable-telemetry. Alternatively, if you would like to specify an initial telemetry level, such as only collecting errors, you can pass in --telemetry-level followed by the level (for example, error).
If telemetry is not disabled via the CLI, the VS Code Server will begin respecting the client telemetry settings (your telemetry setting in vscode.dev or desktop) upon successful connection.
Common Questions
Is the VS Code Server designed for multiple users to access the same remote instance?
No, an instance of the server is designed to be accessed by a single user.
Can I host the VS Code Server as a service?
No, hosting it as a service is not allowed, as specified in the VS Code Server license.
Is there a list of endpoints the VS Code Server uses?
If you're working in a restricted environment, you may need to ensure the VS Code Server has access to the following endpoints:
- https://code.visualstudio.com/docs/setup/network#_common-hostnames
- https://code.visualstudio.com/docs/remote/ssh#_what-are-the-connectivity-requirements-for-the-vs-code-server-when-it-is-running-on-a-remote-machine-vm
Are there any other extension limitations?
Pure UI extensions are not supported when using a web-based instance of VS Code, which you can learn more about in the extension authors Remote Development guide.
Are there browser limitations?
While working in the browser, there are certain limitations and configuration steps to consider. You can read more about this in the VS Code for the Web documentation.
How can I keep the VS Code Server up-to-date?
You will get a notification in VS Code when you connect to your remote machine if an update is available, and you'll be able to update directly through this notification.
I see an error about keyring storage. What should I do?
Settings Sync requires authentication against a Settings Sync server. The corresponding secret is persisted on the server. This requires to set up a keyring on the server. When the keyring is not set up, the VS Code Server falls back to an in-memory secret stored on the server. In this case, secrets are only persisted during the lifetime of the server.
This issue provides more context and may help you troubleshoot. If you're still experiencing issues, please feel free to file a new issue in the VS Code Remote GitHub repo.
Where can I provide feedback or report an issue?
If you have any issues or feedback, please file an issue in the VS Code Remote GitHub repo. When filing an issue, include verbose logging, which you can enable by launching the VS Code Server with the -v flag: code -v tunnel.
You may filter just for VS Code Server issues with the code-server label.