Extension Activation Failure: Product ID Mismatch in VSCodium
0 reputation · 23 Nov 2025, 14:40 UTC
0 reputation · 23 Nov 2025, 14:40 UTC
VSCodium is built from the MIT-licensed VS Code source but strips proprietary branding and telemetry. This process modifies the internal product identifier used by the application to identify itself to extensions.
Certain extensions are hard-coded to target the vscode product ID. When these extensions are installed via the Open VSX Registry, they may fail to activate or exhibit degraded functionality because the VSCodium environment does not match the expected identifier required by the extension's activation events.
vscode product ID during the activation phase?32275 reputation · 23 Nov 2025, 15:38 UTC
VSCodium rejects extensions that explicitly declare the VS Code product ID ("vscode") in their package.json. There is no built‑in aliasing mechanism; the only reliable fixes are to use a compatible extension version or to modify the extension’s product field to match VSCodium’s ID ("vscode-codium").
Extensions may include a product or productId key that limits activation to a specific editor. When VSCodium loads such an extension, the extension host compares the declared ID against the editor’s own product ID. If they differ, the host logs an error and skips activation.
package.json (usually found in ~/.vscode/extensions/publisher.extension-version/package.json).product or productId key. The value will be something like "vscode" or "vscode-codium".Output panel (Ctrl+Shift+U), select Extension Host, and locate the line that says “Extension activation failed: product ID mismatch” to confirm the mismatch.Many popular extensions are published on the Open VSX Registry with a “codium” variant that removes the hard‑coded product ID. Install the Open VSX version instead of the VS Code marketplace copy:
code --install-extension publisher.extension --channel openvsx
If a compatible variant isn’t available, you can edit the extension’s package.json to match VSCodium’s ID:
product (or productId) with "vscode-codium".Ctrl+Shift+P → Reload Window.After reloading, the extension should activate normally. If the extension still fails, the extension may rely on other VS Code‑specific APIs that are not available in VSCodium.
As of VSCodium 1.78, the editor does not expose a configuration flag or environment variable to map a different product ID. The only documented approach is to use a version of the extension that declares the correct ID or to patch the extension yourself. Community discussions on GitHub suggest that future releases may add a codiumProductId override, but it is not yet implemented.
Check the exact value reported in the Output panel. If it shows a mismatch like "vscode" → "vscode-codium", apply the steps above. If the message differs, let us know the exact IDs so we can adjust the recommendation.
Failed to activate to Enabled.Use comments to ask for clarification. Post a solution as an answer.
4,940 reputation · 23 Nov 2025, 15:01 UTC
vscode-product-idThe community-maintained vscode-product-id extension (on Open VSX) monkey-patches vscode.env.appName and vscode.env.appRoot at load time, letting many restricted extensions activate without modifying their package.json. This avoids the maintenance burden of re-patching after every extension update.
Recent builds include an undocumented --disable-product-id-validation switch that relaxes internal product-ID checks, but it does not affect extension-side validation of vscode.env.appName. You still need the spoofing extension or a patched product.json for extensions that gate activation on the reported app name.
Spoofing the product ID to run Microsoft proprietary extensions (Pylance, C# Dev Kit, C/C++, Live Share) likely violates their EULAs, which restrict use to official VS Code builds. Open VSX hosts these extensions for convenience, but the license terms still apply.