ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #vscodium
Choose Vscodium to remove VS Code telemetry, but verify OpenVSX extension coverage and manual .vsix installation before switching.
Vscodium removes telemetry and uses Open VSX by default. Learn how to pin versions, sideload .vsix extensions, and verify gallery endpoints in restricted networks.
VSCodium strips Microsoft’s telemetry and redirects the extension marketplace to Open VSX. Learn how the automated build process works, how to verify the changes, and what limitations to expect when you switch from VS Code to a fully open‑source editor.
Learn how to run VSCodium from a USB stick without leaving any settings, extensions, or cache on the host computer, and understand the trade‑offs of portable mode.
Vscodium’s Remote‑SSH lets you edit and debug code on a remote server as if it were local. Learn how to set it up, run a Node.js example, and understand the trade‑offs.
Learn how Vscodium removes Microsoft telemetry by default, verify its settings, and safely manage extensions from Open VSX or the Microsoft Marketplace.
Learn how to run Vscodium in portable mode by storing settings and extensions in a local data folder next to the executable, keeping the host profile clean.
Vscodium replaces Microsoft's extension marketplace with Open VSX by patching product.json. Here is how that works, where it breaks, and how to verify your gallery settings.
When an extension isn’t in VSCodium’s default Open VSX gallery, install it from a trusted .vsix file instead of repointing the marketplace. This article explains the mechanism, shows a concrete example, and lists limits and common pitfalls.