VS Code Remote Tunnels lets you open a development environment on your desktop from a browser or another VS Code client. On the desktop that will host your project, open the Account menu and select Turn on Remote Tunnel Access, then sign in when prompted. The browser is the interface; your code and development environment stay on the host machine.
Turn on Remote Tunnel Access from VS Code
-
Open VS Code on the desktop that will host the project and its development tools.
As an Amazon Associate I earn from qualifying purchases.
-
Open the Account menu and choose Turn on Remote Tunnel Access. You can also open the Command Palette and run Remote Tunnels: Turn on Remote Tunnel Access….
Recommended: Crashes or Glitches? A Free Driver Scan Usually Finds the Culprit →Recommended: Fix Windows Errors and Clear Junk Files in Minutes - Free Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Sign in with the account requested by VS Code. When the tunnel starts, use the vscode.dev link shown in the notification on the device you want to connect from.
The Account-menu and Command Palette entry points are documented in Microsoft’s Remote Tunnels guide. Microsoft’s VS Code 1.74 release notes also record the menu entry’s introduction in November 2022.
What the tunnel does—and where your code runs
A tunnel connects the client to VS Code Server on the remote machine. Your workspace and development environment remain on that host; the browser or desktop VS Code client provides the interface. Microsoft’s VS Code Server documentation describes this server-side setup, and the Remote Tunnels guide explains how the Remote – Tunnels extension facilitates the connection. With a suitable workflow, you can use features such as IntelliSense, code navigation, and debugging against code hosted on the remote machine.
This is different from opening vscode.dev by itself. Browser VS Code has limitations involving runtimes, terminals, debuggers, and extension support. A tunnel can give the browser access to a remote environment, but it does not make every browser feature identical to desktop VS Code. Microsoft describes the browser editor’s capabilities and constraints in its VS Code for the Web documentation.
Start a tunnel from the command line
If you prefer not to enable the tunnel through the desktop interface, run code tunnel on the machine that will host the project. The command downloads and starts VS Code Server as needed, then creates a tunnel. On its first run, accept the server license terms. The CLI prints a vscode.dev URL; the first client connection requires sign-in to the tunneling service.
The code command-line interface is included with VS Code Desktop. Microsoft also offers a standalone CLI for systems where installing the full desktop application is unsuitable or unavailable. The command-line tunnel can run independently of the desktop UI.
Keep the host available
The desktop must be powered on, connected, and running the process that hosts the tunnel. With the UI-enabled tunnel, the machine is reachable while VS Code remains running there; closing VS Code makes it unavailable through that tunnel until VS Code starts again or a CLI tunnel is run. Plan for the host’s sleep and power settings if you need access while away; behavior depends on your operating system and setup.
To stop an active CLI tunnel, use Ctrl+C in its terminal. To remove a machine association, run code tunnel unregister or remove it through Remote Explorer.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchAuthentication and network behavior
Microsoft says that hosting and connecting to a tunnel require authentication with the same GitHub or Microsoft account. Its documentation describes VS Code making outbound connections to an Azure-hosted service, generally without requiring firewall changes or setting up network listeners. For remote VS Code connections, Microsoft describes an SSH connection over the tunnel for end-to-end encryption and identifies AES 256 in CTR mode as the then-preferred cipher. These are Microsoft’s documented design details, not an independent security audit or a guarantee that every organization’s network and sign-in policies will allow the connection.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
