code-server is an MIT-licensed TypeScript project from Coder that runs VS Code on a remote machine and serves the full editor in a browser, aimed at developers who want one consistent development environment reachable from any device.

What it is

code-server is a browser-based distribution of VS Code. It takes the editor and runs it on a remote host — a cloud server, a home lab box, a workstation — and exposes it over the network so the interface loads in a browser tab. The project lives in the Coder ecosystem alongside coder/coder, the separate product the same company builds for teams adopting remote development, and it carries the topics browser-ide, dev-tools, development-environment, ide, remote-work, vscode, and vscode-remote.

The concrete problem it solves is environment drift and machine dependence. Instead of installing and syncing an editor across a laptop, a desktop, and a borrowed machine, a developer points a browser at one server that holds the code, the toolchain, and the running processes. It replaces the local installation of VS Code for people who want the editor to follow the server rather than the device. Intensive work — tests, compilations, downloads — runs on that server, which keeps the client machine's battery and CPU out of the loop.

Key capabilities

• Runs VS Code in a browser so the editor is reachable from any device with a network connection to the host.
• Ships an install script, install.sh, invoked as curl -fsSL https://code-server.dev/install.sh | sh, which automates setup and uses the system package manager where possible.
• Supports a dry run of that script with curl -fsSL https://code-server.dev/install.sh | sh -s -- --dry-run, so the install steps can be previewed before anything changes.
• Offers one-click buttons and guides for deploying to a cloud provider through the coder/deploy-code-server repository.
• Provides a code-server feature for devcontainers, for projects that already use devcontainers in their workflow.
• Can be deployed to a team through coder/coder when code-server needs to be managed across multiple developers and machines.
• Supports manual installation as a distinct path from the install script, for hosts where the automated route does not fit.

Who uses it and how

• Individual developers who keep a cloud server as the place where code, dependencies, and builds live, and connect to it from whatever machine is at hand.
• Developers on the move who want heavy tasks to execute on a server so the local device's battery life is preserved.
• Teams that run a shared remote development setup, using coder/coder to manage code-server across their infrastructure rather than installing it per person.
• Projects already using devcontainers, which can add the code-server feature instead of changing their environment definition.
• Self-hosters deploying to a cloud provider through the one-click guides, on a host that meets the stated minimum of a Linux machine with WebSockets enabled, 1 GB RAM, and 2 vCPUs.

Getting started

The documented path is the install script: curl -fsSL https://code-server.dev/install.sh | sh, which prints instructions for running and starting code-server when it finishes. Alternatives are manual installation, deployment with coder/coder, one-click cloud provider guides, and the devcontainer feature.

How it compares

code-server is not positioned against a paid competitor in these facts; it sits next to coder/coder, the companion product for teams that need remote development managed across an organisation, rather than as a replacement for it. It also relates to VS Code itself, whose editor it serves in the browser, and to devcontainers, where it exists as an addable feature rather than a competing environment format.

When to use it — and when not to

A self-hoster must supply a Linux host with WebSockets enabled and at least 1 GB RAM and 2 vCPUs, and must handle the network exposure of an editor reachable over the browser. Anyone wanting managed multi-developer provisioning should look at coder/coder instead, since code-server alone is the per-machine component. The README itself is sparse — requirements, installation detail, configuration, and the FAQ all live on external documentation pages — so expect to read beyond the repository to run it well.

curl -fsSL https://code-server.dev/install.sh | sh -s -- --dry-run

curl -fsSL https://code-server.dev/install.sh | sh