code-server
VS Code in the browser. Run VS Code on any machine and access it via browser.
External Tool
This open-source tool is maintained externally. View the source on GitHub to learn more or run it yourself.
Browse developer tools →What's next with code-server?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is code-server?
code-server is an open-source tool that enables users to run Visual Studio Code (VS Code) in a web browser. It acts as a server that hosts a local instance of VS Code, allowing remote access to the editor via a web interface. Developers, DevOps engineers, and remote teams use code-server to work on code projects from any device with internet access. The tool solves the problem of requiring a local installation of VS Code, enabling collaboration and remote development without the need for direct access to a machine's desktop environment. It is particularly useful for scenarios where users need to edit code on shared or remote systems, or when working in environments with limited local computing resources.
How it works
code-server is a web server that hosts a locally running instance of VS Code, making it accessible through a browser. It leverages the core of VS Code's functionality while adding a web-based interface for remote interaction. The primary purpose of code-server is to enable users to edit, debug, and manage code projects from any device, provided they can access the server hosting the instance. This is ideal for developers working in cloud environments, remote teams, or situations where local installations are impractical. code-server supports full VS Code features, including syntax highlighting, code navigation, and extension compatibility. It allows users to run custom scripts, manage workspaces, and access terminal functionalities through a web browser. The tool also integrates with remote development workflows, enabling interaction with version control systems like Git.
How to use it
- 1Install code-server on a local machine or remote server using package managers like npm or download binaries from the GitHub repository. 2. Run the server with a command such as `code-server --auth=none` to start the instance without authentication. 3. Access the web interface by navigating to the provided URL in a browser. 4. Use the editor as you would on a local machine, with options to open files, run commands, and connect to remote terminals. Practical tips include configuring secure authentication methods (e.g., password or token-based access), enabling HTTPS for encrypted connections, and setting up reverse proxies for easier access through firewalls or domain names.
What it can do
- Utility
Use cases
Assumptions and limitations
Assumptions
- source: https://github.com/codeserver
- license: MIT — free to use
- privacy: Opens an external demo
Limitations
- Requires a local server or machine to host the code-server instance, limiting offline usability.
- Performance may degrade with large projects or resource-intensive extensions due to browser-based execution.
- Limited support for advanced VS Code features that rely on native system integrations (e.g., desktop notifications).
- Authentication and security configurations demand technical expertise to implement effectively.
- Browser compatibility issues may arise with certain VS Code extensions or custom scripts.
Understanding the result
VS Code in the browser. Run VS Code on any machine and access it via browser.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by codeserver (MIT).
- Built with
- codeserver (https://github.com/codeserver)
- License
- MIT
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Code
- Output
- Output
Built with https://github.com/codeserver. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- codeserver
- License
- MIT
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- /codeserver — GitHub Repository
Upstream project · GitHub
- MIT License
Upstream project
Frequently asked
How does code-server differ from using VS Code directly?
code-server runs VS Code as a web application hosted on a server, allowing remote access via a browser. Unlike direct usage, it requires a local server instance and relies on web technologies for interaction, which may introduce latency or compatibility challenges with certain features.
How does code-server handle extensions and plugins?
code-server supports most VS Code extensions, provided they are compatible with the web-based environment. Extensions that rely on native system APIs (e.g., file system access beyond the server's scope) may not function as expected. Users should test extensions in the web interface before relying on them for critical tasks.
How do I set up code-server with secure authentication?
To secure code-server, use the `--auth=token` or `--auth=password` flag during startup. Generate a unique token or set a password, then access the interface via HTTPS. For enhanced security, deploy behind a reverse proxy (e.g., Nginx) with SSL certificates to encrypt traffic and restrict direct server access.
How does code-server compare to alternatives like VS Code Web or Remote Development?
code-server is distinct from VS Code Web (a browser-based version of VS Code) and Remote Development (which connects to a remote machine via SSH). code-server hosts a full VS Code instance locally and exposes it via a web interface, while Remote Development relies on a remote machine's desktop environment. VS Code Web is a standalone browser app, whereas code-server requires a server setup.
What should I do if code-server fails to load in the browser?
Check for errors in the browser's developer console, which may indicate issues with the server's configuration or network connectivity. Ensure the server is running and accessible via the correct URL. If using HTTPS, verify SSL certificate validity. Restart the server and try accessing it from a different browser or device if problems persist.