VS Code Remote Development
Official documentation for VS Code's remote development extensions: work inside WSL, on a server over SSH, or in a container, with the editor running locally and your tools running where the code lives. Essential for Windows users on WSL and for editing files on a server.
Guide
Other
Microsoft
About an hour to set up
Beginner
Free
What it is
Visual Studio Code's Remote Development documentation covers a set of extensions that split the editor in two: the interface runs on your computer, and a small VS Code server runs where your code is. The main options are WSL (edit and run code inside your Linux distribution on Windows), Remote SSH (work on a server or another machine over SSH) and Dev Containers (work inside a Docker container). The docs explain how each works, how to install it, and common troubleshooting.
Why it matters for this roadmap
- On Windows, the WSL extension is what makes VS Code work properly with files in your Linux home. Running
code .inside Ubuntu opens the folder with extensions, terminals and debugging all running in Linux. Microsoft's WSL documentation recommends this set-up. - On a server, Remote SSH lets you edit configuration files and code with a full editor instead of only nano or Vim, using the same
~/.ssh/confighost names as your terminal.
How to get started
- Install VS Code on your computer.
- Install the extension you need: WSL for Windows users, Remote SSH for servers.
- For WSL, open Ubuntu and run
code .in a project folder. - For SSH, add your server to
~/.ssh/config, then choose "Connect to Host" from the command palette. - Install language extensions again on the remote side when VS Code prompts you, since they run where the code runs.
Things to know
- The remote side needs enough memory to run the VS Code server; very small servers can struggle.
- Remote SSH is a convenience, not a replacement for knowing a terminal editor. Keep basic nano or Vim skills for emergencies.
- Treat remote servers carefully: editing production files live is risky, and changes should usually go through Git.
Is it worth it?
Yes, especially on Windows. It removes most of the friction of developing in WSL and is free.
Common questions
Does it cost anything? No. VS Code and these extensions are free.
Does it work with VS Codium or other forks? Microsoft's remote extensions are licensed for VS Code itself; forks use alternatives with their own limits.
Do I still need to learn the terminal? Yes. The editor helps you edit; the terminal is still where you run, debug and deploy.
Ready to start?
Opens on Microsoft in a new tab.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
Follow along
New writing, resources and project ideas land here first.