Developing with Remote Tunnels
The Visual Studio Code Remote - Tunnels extension lets you connect to a remote machine, like a desktop PC or virtual machine (VM), via a secure tunnel. You can connect to that machine from a VS Code client anywhere, without the requirement of SSH.
Tunneling securely transmits data from one network to another via Microsoft dev tunnels.
This can eliminate the need for source code to be on your VS Code client machine since the extension runs commands and other extensions directly on the remote machine.
VS Code can provide a local-quality development experience - including full IntelliSense (completions), code navigation, and debugging - regardless of where your code is hosted.
You have two paths to work with tunnels:
- Run the
tunnelcommand of the
codecommand-line interface (CLI).
- Enable tunneling through the VS Code Desktop UI.
Both of these paths result in the same tunneling functionality – you can use whichever tooling works best for you. The CLI is a great option if you can't install the full VS Code Desktop on your remote machine. Using the VS Code Desktop UI is convenient if you're already doing some work in VS Code and would then like to enable tunneling for your current machine.
We'll describe both paths in the sections below.
Using the 'code' CLI
You may create and use tunnels through the
codeCLI on a remote machine you'd like to develop against from a VS Code client. The CLI establishes a tunnel between a VS Code client and your remote machine. The CLI is automatically built into VS Code Desktop – no additional setup required.
Alternatively, you can grab the CLI through a standalone install on our download page, which is separate from a VS Code Desktop installation:
You can also install and unpack the CLI through the terminal of your remote machine. This may be especially helpful if your remote doesn't have a UI:
curl -Lk 'https://code.visualstudio.com/sha/download?build=stable&os=cli-alpine-x64' --output vscode_cli.tar.gz tar -xf vscode_cli.tar.gz
Note: If you're using the standalone or terminal install, the commands in the following section will start with
Create a secure tunnel with the
This command downloads and starts the VS Code Server on this machine and then creates a tunnel to it.
Note: You will be prompted to accept the server license terms when you first start a tunnel on a machine. You can also pass
--accept-server-license-termson the command line to avoid the prompt.
This CLI will output a vscode.dev URL tied to this remote machine, such as
https://vscode.dev/tunnel/<machine_name>/<folder_name>. You can open this URL on a client of your choosing.
When opening a vscode.dev URL for the first time on this client, you'll be prompted to log into your GitHub account at a
https://github.com/login/oauth/authorize...URL. This authenticates you to the tunneling service to ensure you have access to the right set of remote machines.
Using the VS Code UI
Open VS Code on the remote machine where you'd like to turn on tunnel access.
In the VS Code Account menu, select the option to Turn on Remote Tunnel Access, as demonstrated in the image below. You may also open the Command Palette (F1) in VS Code and run the command Remote Tunnels: Turn on Remote Tunnel Access....
You'll be prompted to log into GitHub. Once you're logged in, a tunnel will start up on your current machine, and you'll be able to connect to this machine remotely.
In a client of your choice, you may open the vscode.dev link from the notification above and start coding!
Note: The remote machine will only be reachable through a tunnel while VS Code remains running there. Once you exit VS Code it will no longer be possible to tunnel to it until you start VS Code there again or run the
code tunnelCLI command.
Remote Tunnels extension
The vscode.dev instances you open through the
code CLI or VS Code UI come with the Remote - Tunnels extension preinstalled.
If you're already working in VS Code (desktop or web) and would like to connect to a remote tunnel, you can install and use the Remote - Tunnels extension directly. Once you install the extension, open the Command Palette (F1) and run the command Remote Tunnels: Connect to Tunnel. You'll be able to connect to any remote machines with an active tunnel.
You can also view your remote machines in the Remote Explorer, which you may focus on through the command Remote Explorer: Focus on Remote View:
Like the other Remote Development extensions, the name of your remote machine will be listed in the lower left green remote indicator. Clicking on this indicator is another way to explore Remote Tunnels commands, along with options to close your remote connection or install VS Code Desktop.
Open a folder on a Remote Tunnels host in a container
You can use the Remote - Tunnels and Dev Containers extensions together to open a folder on your remote host inside of a container. You do not even need to have a Docker client installed locally.
To do so:
- Follow the installation steps for installing Docker on your remote host and VS Code and the Dev Containers extension locally.
- Follow the Getting Started instructions for the Remote - Tunnels extension to set up a tunnel, connect to it and open a folder there.
- Use the Dev Containers: Reopen in Container command from the Command Palette (F1, ⇧⌘P (Windows, Linux Ctrl+Shift+P)).
The rest of the Dev Containers quick start applies as-is. You can learn more about the Dev Containers extension in its documentation. You can also see the Develop on a remote Docker host article for other options if this model does not meet your needs.
What is the relationship between the Remote Tunnels, VS Code Server, and Remote Development?
Visual Studio Code Remote Development allows you to use a container, remote machine, or the Windows Subsystem for Linux (WSL) as a full-featured development environment.
Remote Development lets your local VS Code installation transparently interact with source code and runtime environments on other machines (whether virtual or physical) by moving the execution of certain commands to a "remote server", the VS Code Server. The VS Code Server is quickly installed by VS Code when you connect to a remote endpoint and can host extensions that interact directly with the remote workspace, machine, and file system.
We've released this VS Code Server backend component as a service you can run yourself (which you may read more about in its documentation), rather than it only being solely installed and managed by the Remote Development extensions.
Accessing the VS Code Server involves a few components:
- The VS Code Server: Backend server that makes VS Code remote experiences possible.
- Remote - Tunnels extension: Extension that facilitates the connection to the remote machine, where you have an instance of the server running.
As an extension author, what do I need to do?
The VS Code extension API abstracts away local/remote details so most extensions will work without modification. However, given extensions can use any node module or runtime they want, there are situations where adjustments may need to be made. We recommend you test your extension to be sure that no updates are required. See Supporting Remote Development for details.
Can multiple users or clients access the same remote instance simultaneously?
No, an instance of the server is designed to be accessed by one user or client at a time.
How do I remove a tunnel or machine?
If you'd like to stop a tunnel you're running via the CLI, you may use Ctrl + C to end the active tunnel. If you've enabled tunneling through the VS Code UI, you can run the command Remote Tunnels: Turn off Remote Tunnel Access... in VS Code.
You can remove a machine's association with tunneling by running
code tunnel unregister on that machine. You can also open any VS Code client, select the Remote Explorer view, right-click on the machine you'd like to remove, and select unregister.
How are tunnels secured?
Both hosting and connecting to a tunnel requires authentication with the same Github or Microsoft account on each end. In both cases, VS Code will make outbound connections to a service hosted in Azure; no firewall changes are generally necessary, and VS Code doesn't set up any network listeners.
Once you connect from a remote VS Code instance, an SSH connection is created over the tunnel in order to provide end-to-end encryption. The current preferred cipher for this encryption is AES 256 in CTR mode, and the code that implements this is open source.
If you're part of an organization who wants to control access to Remote Tunnels, you can do so by allowing or denying access to the domain
You can learn more about the security of the underlying dev tunnels service in its documentation.
Are there usage limits for the tunneling service?
To avoid abuse of the underlying tunneling service, there are usage limits in place for resources like number of tunnels and bandwidth. We anticipate most users to never reach these limits.
For instance, right now you can have 5 tunnels registered for your account. If you'd like to create a new tunnel and already have 5 others registered, the CLI will pick a random unused tunnel and delete it. Please note this limit is subject to change.
If you are hitting a limit and would like to discuss getting more usage, we'd love to learn more. Please reach out to
firstname.lastname@example.org with information on your scenario and how much usage you need.
How can I ensure I keep my tunnel running?
You have a few options:
- Use the
servicecommand to run as a service. You can run
code tunnel service installand
code tunnel service uninstallto install and remove them.
- Use the
code tunnel --no-sleep, to prevent your remote machine from going to sleep.
As mentioned in the
code CLI doc, you can explore all the possible CLI commands and options through
code tunnel --help.