Visual Studio Code editor: the Code - OSS repo

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.

Other Popular Code Editors

Frequently Asked Questions

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