code-server and OpenVSCode Server: VS Code in your browser
Run VS Code on a server and use it from any browser. What code-server is, what it is known for, and why developers self-host their editor.
code-server runs the VS Code editor on a remote machine and serves it to your browser. You get the VS Code you know — extensions, terminal, debugging — on any device, without installing anything locally.
What it is
code-server — the most popular project for running VS Code on a server, maintained by Coder. It is VS Code (the open-source core) packaged to run headless and reachable over the web.
OpenVSCode Server — a closely related project (from Gitpod) that packages the same upstream VS Code for remote use. The two are technical cousins; code-server has the larger community and friendlier defaults.
What it does
Serves a full VS Code UI in the browser, with a built-in terminal into the server.
Runs your language servers, linters and build tools on the server — so a powerful machine does the work while your laptop only renders the UI.
Keeps your project on the server, so editing, running and testing happen in the same place.
Supports most VS Code extensions and your settings/keybindings.
What it is known for
Coding from anywhere — a Chromebook, tablet or borrowed machine becomes a full dev environment.
Consistent environments — the server has the toolchain, so teammates stop fighting "works on my machine."
Being light to run — a modest VPS handles it; the heavy lifting is your code and builds, not the editor UI.
Why use it
Work from any device with your real environment, not a local approximation.
Keep code off your laptop (useful for a thin client, a locked-down machine, or travel).
One environment for edit + run + test, especially for server-side projects and Docker work.
Accessible by URL behind a domain and TLS, with a password or SSO — no VPN required if you choose.
Where and how
A 2 vCPU, 2–4 GB VPS runs code-server comfortably for one developer; more RAM if you run heavy builds or several language servers. Deploy the official Docker image or the install script, put it behind Nginx/Caddy for TLS, and set a strong password (or put it behind an identity proxy like Authelia/Authentik).
Security note worth repeating: your editor has a terminal into the server. Treat code-server as privileged — always TLS, always authentication, never exposed on a bare port. See /app-hosting/code-server and SSH keys and access.