What you keep and what you drop
Microsoft's own documentation draws the line. The Code - OSS repository is where Microsoft develops the open-source editor that Visual Studio Code is built on. The cited Microsoft wiki says its source is under a standard MIT license. The Microsoft-branded download is a distribution of that code with Microsoft-specific customizations, released under a traditional Microsoft product license.
VSCodium builds the open code into binaries without those additions. Its GitHub project describes itself as binary releases of VS Code without MS branding/telemetry/licensing. It is available on Windows, macOS and Linux. Singh says the core experience carries over:
- File explorer
- Command palette
- Split editor
- Integrated terminal
- Git integration
- The ability to copy over
settings.jsonandkeybindings.json
"Telemetry-free" needs a footnote
Disabling the editor's own telemetry is not the same as having no data collection anywhere in your setup. Microsoft's FAQ warns that VS Code lets you install Microsoft and third-party extensions, and these may collect their own usage data. Those extensions are not controlled by the editor's telemetry.telemetryLevel setting.
The same caveat applies to VSCodium. Its binaries disable Microsoft's product telemetry. Any extension you install can still do its own thing. If privacy is the reason you are switching, check the extensions you rely on, not just the editor.
Why the extension panel looks the same but isn't
VSCodium's extension documentation says Microsoft prohibits usage of its marketplace by any other products. VSCodium therefore ships with product.json set to use open-vsx.org as the extension gallery. The panel looks familiar, but it searches a different catalog.
Microsoft's FAQ states the policy plainly. The Marketplace is provided only for the Visual Studio family of products, and alternative products built on a fork of the Code - OSS repository are not permitted to access it. Microsoft's stated reasons include vetting extensions for security, removing and blocking malicious ones, and keeping API compatibility. Those are Microsoft's arguments. They are not an independent comparison of how safe the two registries are.
The practical result is that a developer who publishes to Microsoft's Marketplace has not automatically published to Open VSX. VSCodium's documented options for a missing extension are:
- Ask the maintainers to publish to Open VSX as well.
- Submit a request to the community publishing repository so a service account publishes it for you.
- Download the VSIX file from the extension's release page and install it manually.
The extensions that don't come along
VSCodium maintains a compatibility guide. It says most Microsoft extensions are limited to Microsoft products by their license and by additional checks in their proprietary code. Its list of incompatible extensions includes:
- C/C++
- Live Share
- Python
- Remote - Containers
- Remote - SSH, and Remote - SSH: Editing Configuration Files
- Remote - WSL
- LaTeX Workshop, which its own maintainers explicitly don't support on VSCodium
The guide also lists replacements:
| Need | Suggested replacement |
|---|---|
| C/C++ editing and IntelliSense | clangd |
| C/C++ debugging (GDB, LLDB) | Native Debug |
| Python analysis | BasedPyright |
| Remote over SSH | Open Remote - SSH |
| Remote in WSL | Open Remote - WSL |
These are VSCodium's recommendations. They don't promise feature parity. Check that a replacement covers your language features, debugging setup and server configuration. There is one concrete requirement for Open Remote - SSH: the SSH server must be configured with AllowTcpForwarding yes. That is easy to miss on a hardened server.
Singh also says Pylance restricts use in unofficial builds. VSCodium's compatibility guide lists Microsoft's Python extension as incompatible. The documents I reviewed don't give a Pylance-specific explanation, so I'm treating that point as Singh's report. Singh also names Prettier, ESLint, Continue and Cline as familiar tools on Open VSX. I haven't verified their current registry status, so check each listing before you depend on it.
Windows developers should also note the C/C++ debugger. VSCodium's docs say the Windows debugger in Microsoft's C++ extension is restrictively licensed to work only with the official Visual Studio Code build. The C# extension's debugger has the same restriction. For C#, the docs point to Samsung's open-source netcoredbg as a workaround.
Tunnels: the feature that is genuinely missing
Singh says he uses VS Code's tunnel feature to reach his desktop remotely, and VSCodium lacks it. Microsoft's documentation describes how the feature works. It is turned on through the Account menu or the command Remote Tunnels: Turn on Remote Tunnel Access.... Hosting and connecting both require authentication with the same GitHub or Microsoft account on each end. VS Code makes outbound connections to a service hosted in Azure. That means a Microsoft-run service is part of the design, which fits with VSCodium leaving it out.
The VSCodium issue tracker points the same way. A user on Arch Linux reported the Ports feature failing with an error saying it could not spawn code-tunnel in the VSCodium bin directory. A separate report that codium tunnel doesn't work was closed as not planned. These are user reports, not an official statement of the product boundary. They are consistent with Singh's account.
Don't confuse tunnels with SSH editing. Singh notes you can still use SSH from the integrated terminal. Editing a remote folder in the editor needs an extension, and that means Open Remote - SSH. It covers SSH-based remote folders. It does not replace Microsoft's tunnel service.
Installing a VSIX: useful, but no loophole
Singh's tip is to look for a VSIX file on the developer's GitHub or official release page and use "Install from VSIX". That works for extensions that run fine outside Microsoft's build. It is a delivery method, not a way around licensing. Singh says so himself. VSCodium's documentation adds that some extensions only work with the official Visual Studio Code build. In some cases the extension is hard-coded to work only with the official product.
VSCodium's docs also describe VSIX Manager, an extension by VSCodium's main maintainer. It can manage .vsix files from local files, GitHub or Forgejo release pages, and multiple marketplaces at once. That helps if you pull extensions from several sources. It can't make an incompatible extension compatible.
A pre-switch checklist
- List the extensions you actually use daily, especially language servers, debuggers and remote tools.
- Look each one up on Open VSX. If one is missing, check the publisher's release page for a VSIX.
- Read the extension's license. Microsoft's FAQ says its own Marketplace extensions are not licensed for use outside the Visual Studio family of products.
- Test the replacements from VSCodium's guide on a real project before you commit.
- If you rely on tunnels, plan a different remote setup, or keep VS Code installed for that job.
- Review the telemetry behavior of the extensions you keep.
The verdict
VSCodium is a reasonable choice if your priorities are an open-source build and no Microsoft product telemetry. It will cost you the least if you work in web languages and common formatters and linters. It will cost the most if you depend on Microsoft's C/C++, Python, Live Share or Remote Development extensions, or on tunnels. Singh says he replaced almost all of what he was missing, but with effort and some digging. That is one developer's experience, not a guarantee. The trade is real, and it's better to find it out in a test run than halfway through a project.
References
- VSCodium ditched Microsoft's telemetry, but it cost me something I didn't see coming XDA · 2026-10-08T21:30:18+00:00
- Differences-between-the-repository-and-Visual-Studio-Code.md github.com
- github.com github.com