Question
VSCodium Extension Gallery Compatibility and Marketplace Constraints
Zo Dey
0 reputation · 23 Jul 2025, 03:30 UTC
42.2K views
Loading…
0 reputation · 23 Jul 2025, 03:30 UTC
VSCodium is distributed as a telemetry-free binary of the VS Code source, utilizing the Open VSX Registry by default to maintain compliance with licensing terms. This differs from the official Visual Studio Code distribution, which connects to the Microsoft Visual Studio Marketplace.
Certain extensions are designed to activate only when the product.json identifies the application as vscode. Because VSCodium modifies these identifiers to remove proprietary branding, some extensions may fail to initialize or lack full functionality despite being available in the registry.
There is an unresolved trade-off between maintaining a strictly telemetry-free environment and achieving full compatibility with extensions that rely on Microsoft-specific product identifiers.
vscode product name for specific extensions without modifying the global product.json?35275 reputation · 23 Jul 2025, 07:26 UTC
No. VSCodium does not provide a native per-extension mechanism to emulate the vscode product name. The only supported way to make extensions that gate on the product identifier activate is to edit the global product.json in the application resources. There is no built-in setting or extension API to spoof the name for a single extension.
Behaviorally, an extension installed from Open VSX in VSCodium and the same extension installed manually as a VSIX from the Microsoft Marketplace both run under VSCodium’s telemetry-free runtime. The difference is in the artifact, not the runtime loader.
vscodiumproduct.json identifying the application as vscodium, not vscode. Extensions that check vscode.env.appName or read the product name will see vscodium unless the file is changed.product.json, e.g. /usr/share/vscodium/resources/app/product.json on Linux, and the change is overwritten by updates.Open VSX versions are often rebuilt by publishers for the open registry. Those builds may omit Microsoft-specific code paths and telemetry dependencies. A manual VSIX is the exact binary published to the Microsoft Marketplace, so it retains Marketplace-only assumptions. In VSCodium both will still run telemetry-free, but a VSIX may contain activation checks or features that assume a vscode product name or Marketplace APIs.
Extensions that gate activation on the product name will fail to initialize in VSCodium regardless of source, Open VSX or VSIX, unless the global product name is changed to vscode. Some publishers provide separate Open VSX variants that remove the product-name check, which can avoid modification.
product.json in the VSCodium installation and confirm the name field.vscode and restart VSCodium to confirm activation changes.Cautions: Editing product.json is global and will be lost on upgrade. Spoofing the name can re-enable code paths that expect Microsoft telemetry or licensing, which conflicts with VSCodium’s telemetry-free goal.
To give a precise recommendation, the specific extension and how it checks the product identifier would change the advice, e.g. activation event vs runtime env.appName check.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.