Code OSS is the source, VS Code is the product

microsoft/vscode is the open source repository for Code OSS, the source tree Microsoft uses to build Visual Studio Code. That sounds like a small naming detail, but it is the first thing to get right. The repository is MIT licensed. The Visual Studio Code product you download from code.visualstudio.com is a distribution of this repository with Microsoft-specific customizations and a Microsoft product license.

The README says this directly, and product.json backs it up: the repository names the OSS build “Code OSS”, uses code-oss as the application name, and points its license URL to the MIT license in the repo. The public product adds branding, services, settings, and release packaging around that base. If your question is “can I read and build the editor source,” the answer is yes. If your question is “is the Microsoft binary exactly the MIT repo,” the answer is no.

As of 2026-06, microsoft/vscode had 186,168 stars, 40,349 forks, and 18,369 open issues. The latest release observed during writing was 1.124.0, published on 2026-06-10. VS Code is still updated monthly, and the repo remains one of the largest public workbenches for editor, extension, AI, terminal, remote, and webview behavior.

Install the editor, or build the source

Most users should not build this repository. They should download Visual Studio Code from the official site:

https://code.visualstudio.com/Download

That gives you Windows, macOS, Linux, and Insiders builds. It is the supported product path.

The repository path is for people who want to work on the editor, inspect Code OSS, patch behavior, or understand the platform. The README points contributors to the wiki for build instructions and recommends the Dev Containers or GitHub Codespaces path. It also notes that a full build container should have at least 4 cores and 6 GB of RAM, with 8 GB recommended. Treat that as a signal: this is a large application, not a small npm package.

Why VS Code became the editor platform

VS Code won because it found a middle ground. It is lighter than a full IDE, but it has enough debugging, language features, terminal integration, settings, and extension APIs to become the default surface for many languages. The built-in extensions in the repo cover grammar and language features for common languages, while richer support comes through the Marketplace and external extensions.

The core product bet was also technical: Electron gave Microsoft a cross-platform desktop shell, TypeScript made the workbench maintainable, and the extension host let the ecosystem grow without every language feature living in the core. That architecture is why VS Code could absorb remote development, notebooks, web UI, Copilot chat, and agent surfaces without turning into a separate product each time.

The price is also visible. VS Code is an application platform, so bugs can come from the workbench, extension host, Electron, webviews, remote tunnels, settings sync, authentication, terminal integration, or an extension. Its issue tracker is huge because it is both an editor and a small operating environment for developer tools.

The 2026 pressure point: agents and Copilot

Recent issues make the current direction clear. VS Code is no longer just competing as a text editor. It is becoming the host for AI agents, model pickers, BYOK flows, chat history, and extension-controlled automation.

Recent feature requests include an agentless version of VS Code (#320850), BYOK support for agent harnesses (#320339), context window support for BYOK models (#320353), files that AI agents should ignore (#320821), and multiple agent-window or agent-host protocol requests. Recent bug reports mention Copilot SDK side effects mutating the shared extension host environment and breaking other extensions (#320880), Copilot login timeouts (#320876), and a WebView resource cache growing without bounds (#320928).

The lesson is not “Copilot is bad” or “agents are ready.” The lesson is that VS Code has become the default place where editor state, model context, Git state, terminal state, webviews, and extensions collide. That makes it powerful. It also means teams using VS Code as an AI-agent host should test extension isolation, model policy, content exclusions, and remote workspace behavior instead of assuming editor features are isolated.

What the open issues tell you

VS Code has more than eighteen thousand open issues as of 2026-06. That number is not a simple quality score. It reflects scale, age, and the fact that users file product, extension, remote, accessibility, webview, terminal, AI, and platform issues in one place.

The high-signal themes are familiar:

Extensions and the extension host. A single extension can affect shared process state, performance, startup, or Git behavior. That is the cost of a powerful extension model.

Webviews and cached resources. VS Code is not only text buffers. It hosts previews, notebooks, extension UIs, media viewers, and embedded browsers. Webview cache behavior can turn into disk or memory problems.

Updates and product surface. Users ask for fewer update prompts, different title bar behavior, and even an agentless edition. This is what happens when a tool sits open all day for years.

Remote and AI workflows. Remote windows, Copilot, BYOK models, and agent-host protocols now sit in the same user journey as editing and debugging.

This is where the README is too small. The repo is best understood as a governance and compatibility machine for a massive extension ecosystem.

Compared with Zed, VSCodium, Lapce, and Void

microsoft/vscode had 186,168 stars as of 2026-06. It is TypeScript, MIT licensed at the Code OSS source level, and best when extension compatibility and ecosystem depth matter most.

zed-industries/zed had 84,997 stars as of 2026-06. It is Rust-heavy and targets performance, collaboration, and a modern editor core. It is the most credible “new editor” comparison, but its extension and compatibility story is not the same as VS Code’s.

VSCodium/vscodium had 31,886 stars as of 2026-06. It is not a different editor architecture. It exists to provide binary releases of VS Code without Microsoft branding, telemetry, and product licensing. Use it when your concern is distribution policy, not editor model.

lapce/lapce had 38,588 stars as of 2026-06. It is Rust, Apache-2.0 licensed, and interesting for people who want a fast editor written outside the Electron tradition.

voideditor/void had 28,813 stars as of 2026-06 and is now archived. It matters as a cautionary VS Code fork: adding AI features was easier than carrying the full upstream fork forever.

The practical answer: choose VS Code when compatibility and ecosystem are the priority. Choose Zed or Lapce when performance and a newer architecture matter more than extension parity. Choose VSCodium when you want the VS Code shape with a different binary policy.

Star curve reading

The star-history data for VS Code is sampled and sparse after the repository became very large. The reliable story is long-term scale, not month-by-month inflection. The repo started in 2015, reached tens of thousands of stars quickly, and remains one of GitHub’s most-starred developer tools in 2026. The live repo data card is more useful than the sampled curve for current rank.

The now-archived voideditor/void page is the useful adjacent read if you want to understand why forking VS Code is expensive. For local model backends that can sit behind editor assistants, see ollama/ollama. For the broader AI tooling stream around editors and agents, follow LLM tooling and the trending repositories hub.

FAQ

Is microsoft/vscode the same as Visual Studio Code? It is the Code OSS source repository used to develop Visual Studio Code. The downloadable Visual Studio Code product includes Microsoft-specific customizations and is released under a Microsoft product license.

Is VS Code open source? Code OSS in this repository is MIT licensed. The Microsoft Visual Studio Code binary is not exactly the same legal artifact as the source repository, which is why VSCodium exists.

How do I install VS Code? Most users should download it from https://code.visualstudio.com/Download. Building this repository is for contributors, packagers, or people inspecting Code OSS.

Why are there so many open issues? VS Code is an editor, extension host, terminal, remote development surface, notebook host, webview platform, and AI-agent surface. The issue count reflects that breadth as much as defect rate.

Should I use VS Code, Zed, VSCodium, or Lapce? Use VS Code for ecosystem depth and extension compatibility. Use VSCodium for a VS Code-like binary policy. Try Zed or Lapce if editor performance and a newer architecture matter more than extension parity.