VSCodium is a community-built distribution of Microsoft’s open-source VS Code codebase. Its build scripts compile the upstream repository with a freely licensed product configuration, remove Microsoft branding and disable the Microsoft telemetry configuration. VSCodium changes the binary distribution and service defaults; it does not create a separate editor codebase with unrelated commands or workspace files.
The extension catalogue is different
VSCodium uses Open VSX as its default extension registry. Microsoft Marketplace terms restrict its offerings to Microsoft Visual Studio products, so the VSCodium project does not support pointing the editor at that marketplace. Open VSX contains many common extensions but does not contain every listing available through Microsoft’s service.
A missing extension can sometimes be installed from a VSIX package. VSCodium also accepts replacement gallery endpoints through environment variables or product.json. Those routes shift the source decision to the user or administrator. A VSIX file does not gain Open VSX review or update behavior merely because VSCodium can install it.
Some Microsoft extensions and remote-development components check licensing or the host product. They can refuse to run or lose functions outside official VS Code. Matching the extension name and version does not remove that product check.
Files, folders and workspaces remain ordinary editor objects
VSCodium opens files, folders and multi-root workspaces through the same upstream editor model. The project describes its output as a binary distribution of upstream source rather than a source-code fork. Settings and extension state normally live in the configured user-data locations. Portable mode changes that placement: when the required portable-data directory exists beside the installation, VSCodium stores its editor data there.
A portable folder can keep settings with a removable copy, but deleting or replacing that data directory removes the local state it contains. The source files in an opened project remain separate from editor configuration. Portable mode does not pack the project itself into VSCodium or automatically copy it beside the executable.
Sandboxed packages need a host bridge
A Flatpak installation runs inside a sandbox. An integrated terminal or extension that needs a host command may not see it directly. The documented workarounds use flatpak-spawn or host-spawn to run outside the sandbox. Adding a command to the host path alone does not guarantee that the sandbox can call it.
GitHub sign-in uses a personal access token, and an extension may request additional token scopes for its own operation. That request belongs to the extension workflow rather than to ordinary file editing. Before granting it, the user can check which repository or account action needs the wider scope. The practical difference between VSCodium and official VS Code therefore appears most clearly in registries, service integrations and packaged environment boundaries rather than in basic text editing.
