microsoft/vscode

Analysis updated 2026-06-20

★ 184,616TypeScriptAudience · developerComplexity · 4/5LicenseSetup · hard

Mindmap

mindmap
  root((VS Code OSS))
    Editor features
      Code navigation
      Debugging
      Rich extensions
    Architecture
      TypeScript codebase
      Electron runtime
      Extension host
    Built-in extensions
      Language grammars
      Snippets
      Language features
    Contribution paths
      Build from source
      Dev container
      GitHub Codespaces

mindmap root((VS Code OSS)) Editor features Code navigation Debugging Rich extensions Architecture TypeScript codebase Electron runtime Extension host Built-in extensions Language grammars Snippets Language features Contribution paths Build from source Dev container GitHub Codespaces

Click or tap to explore — scroll the page freely

What do people build with it?

USE CASE 1

Contribute a bug fix or new feature to VS Code by building the editor locally and submitting a pull request.

USE CASE 2

Study how a large TypeScript and Electron desktop application is structured and maintained for your own editor or desktop app project.

USE CASE 3

Run the VS Code Insiders daily build from source to test unreleased features before they ship.

USE CASE 4

Build a custom VS Code distribution with your own branding using the open-source Code - OSS codebase.

What is it built with?

TypeScriptJavaScriptElectronNode.js

How does it compare?

	microsoft/vscode	n8n-io/n8n	vuejs/vue
Stars	184,616	186,883	209,758
Language	TypeScript	TypeScript	TypeScript
Setup difficulty	hard	moderate	moderate
Complexity	4/5	3/5	3/5
Audience	developer	ops devops	developer

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Full build requires at least 4 CPU cores and 6-8 GB RAM, the Electron-based build pipeline is complex and takes significant time on first run.

The open-source Code - OSS base is MIT licensed, use and modify freely, the VS Code product download has a separate Microsoft product license.

In plain English

This repository, called "Code - OSS," is where Microsoft and the community develop Visual Studio Code, one of the most widely used code editors. The README distinguishes the two: this repo holds the open-source codebase under an MIT license, while the Visual Studio Code product you download from the official website is a distribution of that code with Microsoft-specific customizations and a separate 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 code editing, navigation, and understanding support, plus lightweight debugging, a rich extensibility model, and integration with existing tools. The repo includes a set of built-in extensions in the extensions folder, including grammars and snippets for many languages, and language-features extensions that provide rich support like inline suggestions and Go to Definition for languages like JSON. Many other components and extensions live in their own related repositories. You'd actually use this repo if you want to contribute fixes, build VS Code from source, run the daily Insiders build, or study how a real-world editor is built. For just using the editor, you would download the released binary for Windows, macOS, or Linux from the website. The codebase is TypeScript and runs on Electron, meaning the editor is built like a desktop application using web technologies. The repo also ships a development container configuration for VS Code Dev Containers and GitHub Codespaces, with a recommendation of at least 4 cores and 6 to 8 GB of RAM for a full build.

Copy-paste prompts

Prompt 1

I cloned the microsoft/vscode repo. Walk me through building it from source on macOS with the recommended 4-core, 8GB RAM setup.

Prompt 2

I want to fix a bug in VS Code's JSON language support extension. Which folder in the extensions directory should I look at and how do I test changes locally?

Prompt 3

How do I open and build the VS Code repo inside a GitHub Codespace using the dev container configuration included in the repo?

Prompt 4

Explain how VS Code's extension host architecture works, why does the editor run extensions in a separate process, and how do they communicate?

Frequently asked questions

What is vscode?

This is the open-source codebase for Visual Studio Code, use it to contribute fixes, build the editor from source, or study how a large real-world TypeScript and Electron desktop app is structured.

What language is vscode written in?

Mainly TypeScript. The stack also includes TypeScript, JavaScript, Electron.

What license does vscode use?

The open-source Code - OSS base is MIT licensed, use and modify freely, the VS Code product download has a separate Microsoft product license.

How hard is vscode to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is vscode for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub microsoft on gitmyhub

Verify against the repo before relying on details.