This is not a fork. This is a repository of scripts to automatically build Microsoft’s
vscode repository into freely-licensed binaries with a community-driven default configuration.
Table of Contents
If you are on a Mac and have Homebrew installed:
brew cask install vscodium
Note for Mac OS X Mojave users: if you see “App can’t be opened because Apple cannot check it for malicious software” when opening VSCodium the first time, you can right-click the application and choose Open. This should only be required the first time opening on Mojave.
If you use Windows and have Scoop installed:
scoop bucket add extras scoop install vscodium
You can always install using the downloads (deb, rpm, tar) on the releases page, but you can also install using your favorite package manager and get automatic updates. @paulcarroty has set up a repository with instructions here. Any issues installing VSCodium using your package manager should be directed to that repository’s issue tracker.
flatpak install flathub com.vscodium.codium flatpak run com.vscodium.codium
This repository contains build files to generate free release binaries of Microsoft’s VSCode. When we speak of “free software”, we’re talking about freedom, not price.
When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license.
When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a “clean” build, without the Microsoft customizations, which is by default licensed under the MIT license
This repo exists so that you don’t have to download+build from source. The build scripts in this repo clone Microsoft’s vscode repo, run the build commands, and upload the resulting binaries to GitHub releases. These binaries are licensed under the MIT license. Telemetry is disabled.
Microsoft’s build process (which we are running to build the binaries) does download additional files. This was brought up in Microsoft/vscode#49159 and Microsoft/vscode#45978. These are the packages downloaded during build:
For more information on getting all the telemetry disabled and tips for migrating from Visual Studio Code to VSCodium, have a look at this Docs page.
Extensions and the Marketplace
Please note that some Visual Studio Code extensions have licenses that restrict their use to the official Visual Studio Code builds and therefore do not work with VSCodium. See this note on the Docs page for what’s been found so far and possible workarounds.
How are the VSCodium binaries built?
If you would like to see the commands we run to build
vscode into VSCodium binaries, have a look at the
.travis.yml file (for Linux and OS X builds) and the
win32-build.yml file (for Windows builds). These build files call all the other scripts in the repo. If you find something that doesn’t make sense, feel free to ask about it on Gitter.
If you would like to support the development of VSCodium, feel free to send BTC to