VS Code's shift to the browser
VS Code is constructed from HTML, CSS and JavaScript, yet it is still overwhelmingly used as a locally installed application. That is changing, with a growing number of ways to run it on the web. The stakes are not small: VS Code is the dominant editor among web developers, and a browser-hosted version removes the need to install anything — a real advantage in schools, where software management is burdensome, and on Chromebooks, which are not built around local installs.
vscode.dev: the zero-install local editor
Microsoft recently launched vscode.dev. As Chris Dias explained, browsers supporting the File System Access API (Edge and Chrome at present) let a web page reach the local file system once the user grants permission — a direct path to using VS Code for the Web as a zero-installation local development tool.
Where that API is unavailable, files can still be uploaded, or a repository opened. Where it works, it behaves much like the desktop app: local folders open and basic usage feels equivalent. Some limitations apply. Permission grants are explicit, browser keybindings can conflict with editor shortcuts, and there is no working terminal. Otherwise the experience holds up, including Find in Project, which stays fast even on large sites.
github.dev and GitHub Codespaces
github.dev offers the same editor, wired differently: no local folder access, but a quick way to browse a GitHub repo. Edits can be saved and committed, or turned into a pull request, from the Source Control panel. Whether vscode.dev and github.dev eventually merge is an open question. The reverse direction also works — GitHub repos can be opened in locally installed VS Code without cloning.
GitHub Codespaces goes further: a working terminal, and authentication into Microsoft-land so your local VS Code extensions are available. Its default image ships runtimes and tools for Python, Node.js, Docker and more, and custom images can be configured. On a typical npm project, npm run scripts produce a URL serving a live preview.
Gitpod and container-backed workspaces
Gitpod occupies similar territory: VS Code in the browser with a terminal backed by a full Docker/Linux environment, powerful enough to approximate production when the stack is supported. Its workspaces can run services — in a demo project, MongoDB on one port and a preview server on another, shown in a mock browser interface. Project preview is essential, and Gitpod handles it elegantly.
CodeSandbox, StackBlitz and self-hosting
CodeSandbox and StackBlitz also run VS Code in the browser, or at least something leveraging pieces of it. For those who prefer not to depend on a third party, Coder's code-server installs VS Code on a server you control. Running it on cloud servers puts it alongside your code, making it a full editor for editing files directly on the machine. Schools could host it themselves rather than relying on an external service, and the iPad and Chromebook cases apply more strongly still: per the docs, intensive tasks run on the server, preserving battery life on the go. That also means operations like Find in Project are handled server-side rather than locally.



