Installing Missing VSCodium Extensions with VSIX: A Practical Guide

Why a VSIX is the Right Escape Hatch

VSCodium’s default extension source is the Open VSX gallery. If a required extension is absent from that registry, the simplest and safest way to get it into your editor is to install the exact .vsix artifact with the CLI. Repointing the entire editor to the Microsoft Marketplace changes the behaviour of every extension – search, install, update, and recommendation – and is generally discouraged for repeatable environments.

How VSCodium Resolves Extensions

VSCodium looks up extensions in the URL defined in resources/app/product.json under the key extensionsGallery.serviceUrl. The CLI mirrors that behaviour: codium --install-extension publisher.extension queries the gallery, downloads, and installs the latest matching version. A .vsix bypasses the gallery query entirely; the file is unpacked directly into the extensions directory.

Concrete Example: Installing a Missing Extension

1. Locate a matching VSIX
   • Download the VSIX from the Open VSX website or from the publisher’s release page. Ensure the engines.vscode range in the package.json inside the VSIX matches your VSCodium version (e.g., ^1.85.0).
2. Install the VSIX with the CLI

   # Replace <path-to-vsix> with the actual file location
   codium --install-extension <path-to-vsix>

   Run this in a shell where the codium executable is in $PATH (or use the full path: /usr/bin/codium, C:\Program Files\VSCodium\codium.exe, etc.). The command requires write access to the extensions directory.

3. Verify the installation

   codium --list-extensions --show-versions

   The output should include the installed extension, e.g., publisher.extension@1.2.3. In the Extensions view, the entry appears with a gray “Install from VSIX” badge and no online update button.

4. Optional: Use a specific profile

   codium --user-data-dir <profile-dir> --extensions-dir <extensions-dir> --install-extension <path-to-vsix>

   Passing --extensions-dir and --user-data-dir ensures the VSIX is installed into the desired workspace profile, useful for containerised or CI builds.

Limitations of VSIX Installs

• No Auto‑Update: VSIX‑installed extensions do not receive updates from the gallery. You must manually download and reinstall newer VSIX files.
• Engine Compatibility: If the VSIX’s engines.vscode range does not include your VSCodium version, the extension may fail to activate or be disabled.
• Remote Targets: For SSH, WSL, or web contexts, the extension must also be present on the remote side or installed from a gallery that the remote environment trusts.
• Native Code and Trust: VSIXs can contain native binaries or activate on startup. Install only from trusted publishers and respect workspace trust settings.

Common Mistakes to Avoid

• Assuming a single‑extension fix by editing product.json. That file is global; a change affects all extensions.
• Mixing gallery‑only extensions with VSIX‑installed ones and expecting automatic updates for both.
• Installing a VSIX into the wrong profile directory, causing the extension to be invisible in the intended workspace.
• Forcing installation past engine warnings (e.g., using --force); the extension may not function correctly.

Engineering Decision: When to Use VSIX vs. a Private Gallery

For repeatable, production‑grade builds, consider hosting the required extensions on a private Open VSX mirror or an allow‑listed artifact feed. This preserves the auto‑update path while keeping the default gallery untouched. Reserve VSIX installs for one‑off patches, legacy extensions, or when a publisher has not yet published to Open VSX.

Practical Verification Checklist

Step	What to Check
Confirm Gallery URL	Open resources/app/product.json and verify extensionsGallery.serviceUrl points to Open VSX.
Install VSIX	Run codium --install-extension and observe “Extension installed” message.
List Extensions	Run codium --list-extensions --show-versions and ensure the new extension appears.
Check Activation	Open a file that triggers the extension and verify its functionality.
Profile Isolation	Use --extensions-dir and --user-data-dir flags and confirm the extension is only visible in the target profile.

Conclusion

When a VSCodium extension is missing from the default Open VSX gallery, installing the exact .vsix artifact via the CLI is the most controlled and repeatable approach. It keeps the editor’s global marketplace settings untouched, avoids unintended side effects, and gives you a clear audit trail of the extension version in use. Just remember that VSIX installs are static – you’ll need to manage updates manually or set up a private gallery for automated flow.