
See this article for more information on the motivation behind Open VSX. Create a pull request to this repository to have the service account publish the extensions for you.The publishing process is documented in the Open VSX Wiki. Ask the extension maintainers to publish to in addition to the VS Code Marketplace.You have the following options to obtain such missing extensions: Since that is a rather new project, you will likely miss some extensions you know from the VS Code Marketplace. Extensions + Marketplace How to use the OpenVSX Marketplaceīy default the product.json file is set up to use as extension gallery, which has an adapter to the Marketplace API used by VS Code. Likewise, while the descriptions for "Extensions: Auto Check Updates" and "Extensions: Auto Update" include the same phrase, VSCodium replaces the Visual Studio Marketplace with Open VSX, so these settings won't call Microsoft, either.

When searching the filter, note that while the "Update: Mode" setting description still says "The updates are fetched from a Microsoft online service", VSCodium's build script sets the updateUrl field in product.json to that of VSCodium's own small update server, so enabling that setting won't actually result in any calls to Microsoft servers.

(For example, the C# extension ms-vscode.csharp sends tracking data to Microsoft.) Replacements to Microsoft Online Services We have no control over this and can only recommend removing the extension. Please note that some extensions send telemetry data to Microsoft as well.

You can see those by viewing your VSCodium settings.json and searching for telemetry. We do however set the default telemetry.enableCrashReporter and telemetry.enableTelemetry values to false.

Migrating from Visual Studio Code to VSCodium.How to self host your own VS Code Marketplace.Replacements to Microsoft Online Services.
