Starting with ProGet 2026.12, you can now create Open VSX feeds alongside the many other feed types ProGet already supports.

This feed type lets you host Open VSX-compatible extensions that work with VSCodium and other open-source forks of Visual Studio Code. Once the feed is configured in the editor, developers can browse and install extensions directly from the Extensions view just like they would from a public gallery.

Why a Private Open VSX Gallery?

The official Microsoft build of Visual Studio Code is tied to the Visual Studio Marketplace. Pointing it at a private repository requires unsupported changes that get overwritten on upgrades and may conflict with Microsoft’s license terms.

Open-source alternatives such as VSCodium take a different approach. They can be configured to use any Open VSX-compatible gallery, including one you host yourself in ProGet. This is useful when you want to:

• Distribute internal or company-specific extensions
• Curate a limited set of approved extensions
• Work in air-gapped or highly regulated environments
• Keep extension usage consistent across a team

Introducing Open VSX Feeds

An Open VSX feed stores .vsix packages that follow the Open VSX / VS Code marketplace protocol. It is separate from ProGet’s existing Visual Studio Extension (VSIX) feeds, which are intended for Visual Studio (the full IDE) rather than VS Code-style editors.

You can:

• Upload extensions through the UI, bulk import, or pgutil
• Connect the feed to open-vsx.org (connectors to the official Visual Studio Marketplace are not permitted for licensing reasons)
• Serve the feed to VSCodium and similar tools using the standard gallery endpoints

See the Open VSX Feeds documentation for the full details on creating a feed, uploading packages, and configuring clients.

Using the Feed with VSCodium

To point VSCodium at your ProGet feed, add or edit a product.json file with the gallery endpoints for your feed. After restarting the editor, the Extensions tab will show the contents of the feed and you can install packages as usual.

The exact location of product.json varies by operating system; the documentation includes the common paths for Windows, macOS, and Linux.

A Few Things to Keep in Mind

• Official Microsoft VS Code builds are not supported.
• Only the subset of the Marketplace API that VSCodium and similar tools actually use is implemented.
• The package format and metadata model differ from ProGet’s Visual Studio Extension feeds, even though both use a .vsix file extension.

What’s Next?

We’re always interested in hearing which package types or workflows would be most useful. If there’s another feed type or extension-related capability you’d like to see, let us know on the forums.

For now, the new Open VSX feed type is ready to use: create a feed, drop in a few extensions, point your editors at it, and you’re set.