Visual Studio Code is Microsoft's open-source code editor — the Code - OSS repository, written in TypeScript on Electron and released under the MIT license — and it serves two audiences: developers who want a lightweight editor covering the core edit-build-debug cycle on Windows, macOS, and Linux, and contributors who want to work directly on the editor, its roadmap, and its extensions.
What it is
This repository, referred to in the README as Code - OSS, is where Microsoft and the wider community develop the Visual Studio Code product together. The source is published under the standard MIT license, and the project ships its roadmap, monthly iteration plans, and endgame plans in the open on the project wiki, so the direction of the editor is visible rather than decided behind closed doors. The codebase is TypeScript running on Electron, and the surrounding topics list — editor, electron, microsoft, typescript, visual-studio-code — reflects that stack exactly.
The concrete problem it solves is the fragmentation of the edit-build-debug loop across separate tools: a plain text editor for writing, a separate terminal for building, and another debugger for inspection. Visual Studio Code combines code editing, navigation, and code understanding support with lightweight debugging, a rich extensibility model, and lightweight integration with existing tools. The thing it replaces is that multi-window workflow — and, in the broader market, heavier full-featured IDEs that carry more weight than many edit-build-debug cycles require.
Key capabilities
- Code editing, navigation, and code understanding support with lightweight debugging and lightweight integration with existing tools.
- Rich extensibility model, with core components and extensions such as the
node debug adapter and mono debug adapter maintained in their own GitHub repositories.
- Monthly release cadence for Visual Studio Code, with new features and bug fixes landing each month.
Insiders build for daily releases, aimed at users who want the latest changes every day.
- Cross-platform downloads for Windows, macOS, and Linux from the Visual Studio Code website.
- Open development artefacts: roadmap, monthly iteration plans, and endgame plans published on the project wiki.
- Documentation in a separate
vscode-docs repository, open to pull requests ranging from typo fixes to new content.
Who uses it and how
- Individual developers download the editor for Windows, macOS, or Linux from the Visual Studio Code website and use it as their daily edit-build-debug environment.
- Developers who want changes as soon as they land install the
Insiders build to get releases every day rather than monthly.
- Extension authors connect with the extension author community through GitHub Discussions or the project Slack channel, and follow updates via the
@code account.
- Contributors build and run the editor from source following the
How to Contribute document, which covers the development workflow, debugging, running tests, coding guidelines, and submitting pull requests.
- Translators contribute through the localisation channel published at
aka.ms/vscodeloc, while users ask and answer questions under the vscode tag on Stack Overflow.
Getting started
Download Visual Studio Code for Windows, macOS, or Linux from https://code.visualstudio.com/Download, or install the Insiders build from https://code.visualstudio.com/insiders for daily releases. Developers who want to run the editor from source should follow the How to Contribute wiki document, which covers building and running from source.
How it compares
This registry lists no comparable editor alongside it, so it stands alone here rather than being contrasted with named alternatives. Readers looking for a direct comparison against other editors or IDEs will not find one in these facts.
When to use it — and when not to
Because this is a desktop application rather than a hosted service, adopting it does not commit anyone to operating a database, object storage, or mail server, and the practical running cost is a local install. The honest caveats are on the maintenance side: the issue tracker carries 21,181 open issues, so feature requests and bug reports compete in a very large backlog, and Code - OSS is not the same artefact as the shipped Visual Studio Code, which is a distribution carrying Microsoft-specific customisations under a traditional Microsoft product licence rather than the MIT licence that covers this repository. Anyone expecting the source tree to build byte-for-byte the product they downloaded should check that distinction first, and the README itself is written primarily for contributors, so it documents how to participate rather than how to operate the editor day to day.
project readme (upstream, from github) — read inline
Visual Studio Code - Open Source ("Code - OSS")

The Repository
This repository ("Code - OSS") is where we (Microsoft) develop the Visual Studio Code product together with the community. Not only do we work on code and issues here, but we also publish our roadmap, monthly iteration plans, and our endgame plans. This source code is available to everyone under the standard MIT license.
Visual Studio Code
Visual Studio Code is a distribution of the Code - OSS repository with Microsoft-specific customizations released under a traditional Microsoft product license.
Visual Studio Code combines the simplicity of a code editor with what developers need for their core edit-build-debug cycle. It provides comprehensive code editing, navigation, and understanding support along with lightweight debugging, a rich extensibility model, and lightweight integration with existing tools.
Visual Studio Code is updated monthly with new features and bug fixes. You can download it for Windows, macOS, and Linux on the Visual Studio Code website. To get the latest releases every day, install the Insiders build.
Contributing
There are many ways in which you can participate in this project, for example:
If you are interested in fixing issues and contributing directly to the codebase, please see the document How to Contribute, which covers the following:
Feedback
See our wiki for a description of each of these channels and information on some other available community-driven channels.
Related Projects
Many of the core components and extensions to VS Code live in their own repositories on GitHub. For example, the node debug adapter and the mono debug adapter repositories are separate from each other. For a complete list, please visit the Related Projects page on our wiki.
Bundled Extensions
VS Code includes a set of built-in extensions located in the extensions folder, including grammars and snippets for many languages. Extensions that provide rich language support (inline suggestions, Go to Definition) for a language have the suffix language-features. For example, the json extension provides coloring for JSON and the json-language-features extension provides rich language support for JSON.
Development Container
This repository includes a Visual Studio Code Dev Containers / GitHub Codespaces development container.
For Dev Containers, use the Dev Containers: Clone Repository in Container Volume... command, which creates a Docker volume for better disk I/O on macOS and Windows.
- If you already have VS Code and Docker installed, you can also click here to get started. This will cause VS Code to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use.
For Codespaces, install the GitHub Codespaces extension in VS Code, and use the Codespaces: Create New Codespace command.
Docker / the Codespace should have at least 4 cores and 6 GB of RAM (8 GB recommended) to run a full build. See the development container README for more information.
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
License
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT license.