code-server vs VS Code serve-web vs Remote Tunnels

You want VS Code in a browser, running on a machine you control. Search for it and you'll find three answers that sound similar: code-server, VS Code's own code serve-web command, and Remote Tunnels. They differ in ways that matter later, especially which extensions you can install and who handles networking and sign-in. This post compares them honestly and ends with a table to help you pick.

Three ways to get VS Code in a browser

All three run the VS Code backend on your machine and render the editor in a browser tab. The differences are in who builds it, where extensions come from and how you reach it from another device.

code-server is an open source project from Coder (the company, unrelated to Coder IDE). It packages the open source VS Code core as a web server you run yourself. It's been around since 2019, has a large community and is MIT licensed.

code serve-web is a command in Microsoft's own VS Code CLI. It starts the official VS Code server and serves the web editor locally. It's the same product you install on your desktop, just running headless and served to a browser.

Remote Tunnels is also part of Microsoft's VS Code. Running code tunnel registers your machine with Microsoft's tunnel service, and you connect from vscode.dev or a desktop VS Code. Networking is handled for you.

There are other projects in this space, such as Gitpod's openvscode-server, which behaves much like code-server for the purposes of this comparison.

Extensions: Open VSX vs the Microsoft Marketplace

This is the difference people discover too late.

The Visual Studio Marketplace's terms say its offerings are for use with Visual Studio products only. code-server isn't a Microsoft product, so it uses the Open VSX registry instead. The code-server FAQ explains this and admits Open VSX isn't perfect, though it keeps gaining extensions.

Most popular open source extensions are on Open VSX. What's missing are Microsoft's own closed-source extensions, whose licenses restrict them to Microsoft's builds. The code-server FAQ names Live Share and the Remote extensions (SSH, Containers, WSL). Pylance is the most common pain point for Python developers: its license only allows use with Microsoft's VS Code, which the Pylance maintainers have confirmed. People usually fall back to an open source language server, which works but isn't the same.

code serve-web and Remote Tunnels are Microsoft's build, so they use the Microsoft Marketplace and the extensions you have at your desk.

If your stack depends on Pylance or another Microsoft extension, start with an option that runs Microsoft's VS Code. Swapping later means reconfiguring your editor.

Networking and sign-in

Running a VS Code server is the easy part. Reaching it safely from a phone at a café is the hard part.

code-server gives you a server on a port, with password authentication by default. Remote access is up to you. The common patterns:

• A reverse proxy such as Caddy or nginx with a domain and HTTPS certificates, exposed to the internet.
• A private network like Tailscale, so only your devices can reach it. Tailscale's own guide walks through this setup.
• SSH port forwarding from each client.

All of these work. Each is something you set up, maintain and keep patched.

code serve-web is similar. It listens locally and protects the page with a connection token. Getting to it from outside your network is again your job, with the same options as above.

Remote Tunnels removes the networking work. Your machine connects out to Microsoft's tunnel service, so there's nothing to forward and it works behind NAT. According to the Remote Tunnels docs, both ends must sign in with the same GitHub or Microsoft account, there are usage limits including 10 registered tunnels per account, and the machine is only reachable while VS Code is running on it. We go deeper on its strengths and limits on phones in VS Code Remote Tunnels alternative.

Licensing differences

This only matters if you plan to build something on top, but it's worth knowing:

• code-server is MIT licensed. You can modify it, embed it and redistribute it.
• code serve-web and Remote Tunnels are part of Microsoft's VS Code, distributed under Microsoft's license terms. Using them yourself is fine. Repackaging and redistributing them is a different question, and you should read the terms.

For personal use, licensing rarely changes the decision. Extensions usually do.

What a managed serve-web adds

The gap between code serve-web and a daily setup is everything around it: installing, updating, reaching it securely and keeping it running. That's the part Coder IDE handles. It runs Microsoft's own code serve-web on your computer and adds:

• One install command. Run it on Windows, macOS, Linux or WSL. Click Sign in in the desktop app and confirm the code from a browser you're signed in to. The machine appears on your dashboard.
• Updates. The desktop app and the editor it serves keep themselves up to date. You never re-run the installer.
• No networking work. No port forwarding, VPN or certificates, and it works behind NAT and firewalls. Traffic goes through a relay that forwards it; your code stays on your machine. On the same home network it connects directly and falls back to the relay automatically.
• Device approval. Every new machine must be approved by you, and the approval shows which computer is asking, with a warning if it's on a different network. Remove a device and its token stops working immediately. Sign-in is a one-time email link or Google, with no password to reuse. See security.
• Multiple projects. Open each folder as its own project on the same machine and switch between them.
• Ports and previews. Turn on Allow preview for a dev server's port in the Ports panel and it gets a private link that only opens for you. The Preview button opens the running app beside your code or in its own tab.
• Auto-suspend. Idle editors shut down after a timeout you choose, and wait for running Claude Code tasks to finish first.
• Mobile. Open it from any browser, as an installable web app, or in the Android app with a key bar for Esc, Tab, Ctrl, Alt and arrows.
• Claude Code. See every Claude Code session on your computers, approve requests from your phone and review changes file by file. Review Claude Code's diffs on your phone shows how that works.

What it doesn't change: your editor is still VS Code with your extensions, settings and keybindings, and it still needs your computer to be on.

Decision table

Pick code-server if you want fully open source software, you're comfortable running a reverse proxy or private network, and Open VSX has the extensions you need. It's also the right base if you're building your own product.

Pick code serve-web on its own if you only need the editor on your local network, or you already run a private network and want Microsoft's extensions.

Pick Remote Tunnels if you already use a GitHub account, want zero setup and mostly connect from desktop browsers. It's free and maintained by the VS Code team.

Pick Coder IDE if you want Microsoft's VS Code with managed networking, device approval, mobile apps and Claude Code on your phone, across one or more of your own computers.

Wrap-up

The three options share a codebase but not an experience. code-server trades Microsoft's extensions for an open license. code serve-web gives you the real editor and leaves networking to you. Remote Tunnels handles networking with your GitHub or Microsoft account. Coder IDE runs the same code serve-web and handles the rest around it. If you want to see the wider picture of running everything on your own hardware, read your computer is the best cloud dev environment you own.

Start free. The free plan covers one computer.