Visual Studio Code editor: the Code - OSS repo
/vscode
Visual Studio Code's source lives in this repository, published as Code - OSS under the MIT license. The README is upfront that the branded Visual Studio Code product is a separate Microsoft distribution built from this code, not the repo running unmodified. Reach for this repo to build or debug the editor; reach for the download page instead if you just want VS Code installed.
Understanding Visual Studio Code and Code - OSS
Visual Studio Code, per its own README, is developed in this repository under the name Code - OSS, while the branded Visual Studio Code product is a separate Microsoft distribution of that same code with its own product license. The editor supports the day-to-day edit-build-debug cycle: navigating and understanding code, running a lightweight debugger, and adding capabilities through extensions instead of one monolithic core.
Core Editing and Development Features
- βCombines code editing, navigation, and code understanding with lightweight debugging in one editor, per the README.
- βShips a rich extensibility model, so features live as installable extensions instead of being wired into the core editor.
- βIntegrates lightly with existing command-line tools and workflows, according to the README.
- βBundles built-in extensions inside the extensions/ folder, adding grammar and snippet support across many programming languages, per the README.
- βExtensions with the 'language-features' suffix add richer support such as Go to Definition, distinct from the base grammar/snippet extension for the same language β the README's own json vs json-language-features example.
- βShips a ready-made container setup for Dev Containers and GitHub Codespaces so contributors get a working environment without local setup, per the README.
- βBuilt in TypeScript on Electron, per the GitHub repository's own language and topic metadata.
Getting Started with VS Code
The README doesn't list build commands inline; it says building and running Code - OSS from source is covered on a separate wiki page (How to Contribute), so the exact steps are not clearly documented in the README itself. If you just want the finished editor rather than the source, the README points to the Visual Studio Code website for downloads on Windows, macOS, and Linux, or the Insiders build for a daily-release channel. The repository also ships a Dev Containers / GitHub Codespaces configuration for contributors who'd rather build inside a container than set up a local toolchain.
The Developer Workflow with VS Code
Inside this repo, the workflow the README documents is the contribution cycle: build from source using the linked wiki guide, then use the same debugging and test-running setup described in How to Contribute to work on the editor itself. Using the finished editor day to day isn't this repo's job. That's the download page's job, not this repo's. Contributors instead submit bugs and feature requests, send pull requests against the source, and review documentation changes in the separate vscode-docs repository.
Strengths
- βDevelopment happens out in the open under the MIT license, so anyone can read the roadmap, the monthly iteration plans, and the 'endgame' plans linked from the README instead of guessing where the editor is headed.
- βThe extensibility model keeps optional language support out of the core: the extensions/ folder shows exactly how grammar packages and language-features packages are split per language.
- βFeedback channels are explicit and varied: the Stack Overflow vscode tag, GitHub Discussions, a Slack community, and a public issue tracker where feature requests can be upvoted.
- βA ready-made Dev Containers / Codespaces setup means contributors don't have to hand-build a local toolchain before touching the source.
- βThe README says the editor gets a new release with features and fixes roughly every month, plus a daily-build Insiders channel for anyone who wants changes sooner.
Distinguishing Code - OSS from the Product
- β³This repo builds Code - OSS, not the Microsoft-branded VS Code binary; the README says the branded product adds Microsoft-specific customizations under its own separate product license, so what you compile here isn't identical to what ships from the VS Code website.
- β³Build-from-source steps are not clearly documented in the README itself β it defers entirely to a separate wiki page, so you can't get exact commands without leaving the repo.
- β³The README doesn't give a version number, changelog, or exact release date, only a general monthly release cadence, so you can't tell from the repo alone what shipped most recently.
- β³Building inside the project's own Dev Container needs meaningful hardware: the README calls for a minimum of 4 CPU cores and 6GB of memory, recommending 8GB, before a complete build finishes.
Other Popular Code Editors
Frequently Asked Questions
Code - OSS is this repository's own MIT-licensed source, where Microsoft develops the editor with the community. Visual Studio Code is Microsoft's own branded distribution of that same code, adding Microsoft-specific tweaks and shipping under a separate Microsoft product license, according to the README.
The Code - OSS repository is MIT-licensed, per GitHub's license field and the README's own license section. The branded Visual Studio Code product you download from the website ships under a different, traditional Microsoft product license, separate from this repo's MIT terms.
The README says Visual Studio Code gets a new release with features and fixes roughly every month. If you want changes sooner, the Insiders build offers a daily-release channel instead.
Contributing to Visual Studio Code is documented in the README: you can file and help verify bugs and feature requests, review source code changes through pull requests, or review and write documentation in the separate vscode-docs repository.
Visual Studio Code Insiders builds are a separate download the README points to for getting the latest changes every day, ahead of the regular monthly release.
The problem it solves
Developers who want to see exactly how Visual Studio Code is built, or need to fix or add a feature, can't do that by installing the app from the website: that binary is the Microsoft-branded distribution with its own product license, not the raw source. This repository is where the README says Microsoft actually develops the editor with the community, publishing the roadmap and iteration plans in the open, so it's the place to go when you need the source, the issue tracker, or the build itself rather than just the finished install.
Best use cases
- β’Building and debugging the editor from source to study or extend Visual Studio Code's own internals, since the README documents a How to Contribute guide covering build-and-run and debugging.
- β’Writing or testing an extension, using the bundled extensions/ folder as a reference for how grammar, snippet, and language-features packages are structured.
- β’Filing bugs, upvoting feature requests, or reviewing pull requests as a way to participate without touching code, per the README's Contributing section.
- β’Developing inside the project's own Dev Containers / Codespaces setup instead of hand-building a local toolchain.
Who should try it β and who should skip
Try this repo if you want to build Visual Studio Code from source, write or debug an extension, or follow Microsoft's roadmap and iteration plans out in the open. Skip cloning it if you only want the editor: download the built Visual Studio Code product from its website instead, since that's the Microsoft-branded distribution this repository feeds, not something you assemble yourself for daily use.
Related repositories
Still deciding about vscode?
One click hands the question to an AI along with this page β see what it says about vscode.