VS Code, with the open source kernel codenamed Code OSS, is the open source code editor built by Microsoft and the community, and it is the source repository of the Visual Studio Code product everyone uses daily. It packages editing, navigation, light debugging, and a rich extension model into one place, and it is the default editor for most developers today. Whether you write frontend, backend, scripts, or config, you can almost always find a comfortable workflow on it, and with deep AI assistant integration it has become one of the most mainstream surfaces for the agent era.

What it does

The Code OSS repo is where VS Code product development happens, and beyond code and issues it publishes the roadmap, monthly iteration plans, and wrap up plans. Its output, Visual Studio Code, combines editor simplicity with the core edit, build, and debug loop developers rely on, offering comprehensive code editing, navigation, and understanding support, light debugging, and a rich extension model, plus light integration with existing tools. Essentially, the VS Code you download from the store grew out of this open source kernel, and the two are kept in close sync through the public development process.

What problem it solves

Developers want a lightweight yet complete editor that balances startup speed, cross platform consistency, and a huge extension ecosystem. VS Code makes editing, debugging, and extensions work out of the box across Windows, macOS, and Linux, ships monthly feature and fix releases, and offers a daily Insiders build. It handles both a quick config tweak and a large project daily work, and with the Remote family of extensions you can write code directly inside a remote machine or container. Add AI assistants and it covers the full range from beginner to pro, which is why it became the default rather than just another editor.

Language and architecture

The main language is TypeScript, the desktop shell is Electron (Chromium plus Node.js), and the editor core, language features, and extension host are all TypeScript, with extensions plugged in through contribution points and an API. The Code OSS repo is MIT licensed, while the official VS Code product adds Microsoft customization and ships under the Microsoft product license. Topics are tagged editor, electron, microsoft, typescript, and visual studio code. The repo was created in September 2015, is one of the default editors for developers, and sits at roughly 195k stars with an unmatched ecosystem that spans languages, debuggers, and cloud tooling.

License

The Code OSS repo is MIT licensed, free to view, build, and distribute. The official VS Code product uses the Microsoft product license, so the kernel is shared but the packaging and trademark differ, and the OSS build is what you get if you compile it yourself.

As the default editor for developers, VS Code tops the charts year after year. In 2026, with GitHub Copilot and similar AI coding deeply integrated and monthly stable iterations, it remains one of the most mainstream surfaces in the agent era. It gained about 301 stars on its launch day. It is often compared with the native class What Is Zed and How to Use It, and if you also want a Linux dev environment on Windows, see Install and Set Up WSL2 on Windows to Run Linux, since the VS Code plus WSL combo is many people standard stack for web and backend work.

Where to find it

GitHub repo https://github.com/microsoft/vscode .

Getting started

Newcomers download the stable build, install a few common extensions such as language support, formatting, and Git integration, and start working. For large or remote projects, pair the Remote SSH and WSL extensions to move the dev environment onto a remote box or the Linux subsystem for the most complete experience. To try bleeding edge, install Insiders, but keep your main work on stable so daily updates don't interrupt your rhythm, and export your settings so a reinstall is painless.

FAQ

Is Code OSS the same as the VS Code I download from the store? The kernel is shared, but the official product adds Microsoft customization and trademark, and the license differs. Community OSS builds have none of those extras and are lighter, though some first party integrations are absent.

Why does it feel heavy on resources? The foundation is Electron (Chromium plus Node.js), so overhead is higher than a native editor, but you get cross platform consistency and an extension ecosystem, which is acceptable on most dev machines and tunable through settings.

Is Insiders worth using? It is good for first access to new features, but it updates often and is occasionally unstable, so keep your main development on stable and don't spend time debugging the editor itself.

Can I use it for remote development? Yes, the Remote SSH, WSL, and Containers extensions are a big reason people stay, letting you edit code as if it were local while it runs elsewhere.