### Install VSCodium with Scoop (Windows)

Source: https://github.com/vscodium/vscodium/blob/master/README.md

Use Scoop to install VSCodium on Windows. First add the extras bucket with 'scoop bucket add extras', then install with 'scoop install vscodium'.

```bash
scoop bucket add extras
scoop install vscodium
```

--------------------------------

### Install VSCodium with Flatpak (GNU/Linux)

Source: https://github.com/vscodium/vscodium/blob/master/README.md

Install VSCodium as a Flatpak app on GNU/Linux distributions with Flatpak support. First install the app with 'flatpak install flathub com.vscodium.codium', then run it with 'flatpak run com.vscodium.codium'.

```bash
flatpak install flathub com.vscodium.codium
flatpak run com.vscodium.codium
```

--------------------------------

### Verify Windows Build Tool Installation

Source: https://github.com/vscodium/vscodium/blob/master/docs/howto-build.md

Verify that all required build tools are discoverable from Git Bash on Windows. Run each command to confirm the expected version or output; if any command is not found, add its install directory to PATH via System Properties.

```bash
node --version    # should match .nvmrc
npm --version
jq --version
python3 --version # should be 3.11.x
cargo --version
7z i 2>&1 | head -1
git --version
```

--------------------------------

### Install VSCodium with WinGet (Windows)

Source: https://github.com/vscodium/vscodium/blob/master/README.md

Use Windows Package Manager (WinGet) to install VSCodium on Windows. The stable version is installed with 'winget install -e --id VSCodium.VSCodium' and the insiders version with 'winget install -e --id VSCodium.VSCodium.Insiders'.

```cmd
:: stable
winget install -e --id VSCodium.VSCodium

:: insider
winget install -e --id VSCodium.VSCodium.Insiders
```

--------------------------------

### Install Required Windows Development Tools

Source: https://github.com/vscodium/vscodium/blob/master/docs/howto-build.md

Install required Windows tools for building VSCodium. Each command installs one of the required tools: Git for Windows, Node.js (via nvm-windows), jq, 7-Zip, Python 3.11, and Rustup. After installation, some tools need PATH updates or shell restarts as noted in the documentation.

```cmd
winget install --id Git.Git -e
```

```cmd
nvm install <version-from-.nvmrc>
nvm use <version-from-.nvmrc>
```

```cmd
winget install --id jqlang.jq -e
```

```cmd
winget install --id 7zip.7zip -e
```

```cmd
winget install --id Python.Python.3.11 -e
```

```cmd
winget install --id Rustlang.Rustup -e
```

--------------------------------

### Install VSCodium with Chocolatey (Windows)

Source: https://github.com/vscodium/vscodium/blob/master/README.md

Use Chocolatey to install VSCodium on Windows. The stable version is installed with 'choco install vscodium' and the insiders version with 'choco install vscodium-insiders'.

```cmd
:: stable
choco install vscodium

:: insider
choco install vscodium-insiders
```

--------------------------------

### Install VSCodium with Homebrew (Mac)

Source: https://github.com/vscodium/vscodium/blob/master/README.md

Use Homebrew to install VSCodium on macOS. The stable version is installed with 'brew install --cask vscodium' and the insiders version with 'brew install --cask vscodium@insiders'.

```bash
# stable
brew install --cask vscodium

# insiders
brew install --cask vscodium@insiders
```

--------------------------------

### Install VSCodium with Snap (GNU/Linux)

Source: https://github.com/vscodium/vscodium/blob/master/README.md

Install VSCodium as a Snap package on GNU/Linux distributions with snap support. The command 'snap install codium --classic' installs the stable version.

```bash
snap install codium --classic
```

--------------------------------

### Example: Set Update: Mode to none

Source: https://github.com/vscodium/vscodium/blob/master/docs/troubleshooting.md

Example registry values to set the 'Update: Mode' policy to 'none'. Use REG_SZ type with value name 'update.mode'.

```text
Registry key: HKLM\SOFTWARE\Policies\VSCodium\VSCodium
Value name:   update.mode
Value type:   REG_SZ
Value data:   none
```

--------------------------------

### Open files or directories with codium command

Source: https://github.com/vscodium/vscodium/blob/master/docs/usage.md

After installing the 'codium' command in PATH, use these commands to open the current directory or a specific file from the terminal.

```bash
~/in-my-project $ codium . # open this directory
~/in-my-project $ codium file.txt # open this file
```

--------------------------------

### Manual context menu registry entries

Source: https://github.com/vscodium/vscodium/blob/master/docs/troubleshooting.md

Adds 'Open with VSCodium' to the Windows Explorer file context menu via Registry Editor. Adjust the install path to match your actual installation.

```text
Key:   HKEY_CLASSES_ROOT\*\shell\Open with VSCodium
Value: (Default) = "Open with VSCodium"

Key:   HKEY_CLASSES_ROOT\*\shell\Open with VSCodium\command
Value: (Default) = "C:\Program Files\VSCodium\VSCodium.exe" "%1"
```

--------------------------------

### Set default file manager in mimeapps.list

Source: https://github.com/vscodium/vscodium/blob/master/docs/usage.md

Create ~/.config/mimeapps.list with this content to set the default file manager for directories, replacing the example with your preferred file manager.

```ini
[Default Applications]
inode/directory=org.gnome.Nautilus.desktop;
```

--------------------------------

### Fix rendering glitches on Linux (flatpak GPU cache)

Source: https://github.com/vscodium/vscodium/wiki/Troubleshooting

Deletes the GPU cache for the flatpak installation of VSCodium to fix rendering glitches on Linux.

```bash
rm -rf ~/.var/app/com.vscodium.codium/config/VSCodium/GPUCache
```

--------------------------------

### Add extension IDs to extensionAllowedProposedApi in product.json

Source: https://github.com/vscodium/vscodium/blob/master/docs/extensions.md

Add the internal IDs of proprietary extensions to the extensionAllowedProposedApi property in your VSCodium product.json to enable them. This example shows the Remote Development extensions, but the change may not work if the extension is hard-coded to only work with the official build.

```jsonc
   "extensionAllowedProposedApi": [
      // ...
      "ms-vscode-remote.vscode-remote-extensionpack",
      "ms-vscode-remote.remote-wsl",
      // ...
   ],
```

--------------------------------

### Build Snap Package

Source: https://github.com/vscodium/vscodium/blob/master/docs/howto-build.md

Commands to build a Snap package for the stable or insider version, then verify it with review-tools.snap-review.

```bash
# for the stable version
cd ./stores/snapcraft/stable

# for the insider version
cd ./stores/snapcraft/insider

# create the snap
snapcraft --use-lxd

# verify the snap
review-tools.snap-review --allow-classic codium*.snap
```

--------------------------------

### Run codium with X11 Ozone platform

Source: https://github.com/vscodium/vscodium/blob/master/docs/troubleshooting.md

Run codium with the X11 Ozone platform as a workaround for EGL driver errors under Wayland.

```bash
codium --ozone-platform=x11
```

--------------------------------

### Flatpak: Execute commands on host system

Source: https://github.com/vscodium/vscodium/blob/master/docs/troubleshooting.md

Run these commands inside the Flatpak sandbox to execute commands on the host system.

```bash
flatpak-spawn --host <COMMAND>
# or
host-spawn <COMMAND>
```

--------------------------------

### Configure custom extension gallery in product.json

Source: https://github.com/vscodium/vscodium/blob/master/docs/extensions.md

Place this JSON in a custom product.json file to configure a different extension gallery. The serviceUrl, itemUrl, and extensionUrlTemplate fields are required; the others are optional. The file location varies by OS: Windows uses %APPDATA%\VSCodium or %USERPROFILE%\AppData\Roaming\VSCodium, macOS uses ~/Library/Application Support/VSCodium, and Linux uses $XDG_CONFIG_HOME/VSCodium or ~/.config/VSCodium.

```jsonc
{
   "extensionsGallery": {
      "serviceUrl": "", // required
      "itemUrl": "", // required
      "cacheUrl": "",
      "controlUrl": "",
      "extensionUrlTemplate": "", // required
      "resourceUrlTemplate": "",
   }
}
```

--------------------------------

### Run codium with verbose logging

Source: https://github.com/vscodium/vscodium/blob/master/docs/troubleshooting.md

Run codium with verbose logging to diagnose window display issues under Wayland.

```bash
codium --verbose
```

--------------------------------

### Base CI/downstream build script with environment variables

Source: https://github.com/vscodium/vscodium/blob/master/docs/howto-build.md

Use this script in CI or downstream packaging to build VSCodium. It exports required environment variables (SHOULD_BUILD, SHOULD_BUILD_REH, CI_BUILD, OS_NAME, VSCODE_ARCH, VSCODE_QUALITY, RELEASE_VERSION) and sources get_repo.sh and build.sh. The script is for CI/downstream purposes; the dev/build.sh script is for development only.

```bash
# Export necessary environment variables
export SHOULD_BUILD="yes"
export SHOULD_BUILD_REH="no"
export CI_BUILD="no"
export OS_NAME="linux"
export VSCODE_ARCH="${vscode_arch}"
export VSCODE_QUALITY="stable"
export RELEASE_VERSION="${version}"

. get_repo.sh
. build.sh
```

--------------------------------

### Manual Patch Update Process

Source: https://github.com/vscodium/vscodium/blob/master/docs/howto-build.md

Commands to manually update a specific patch when it fails during build.

```bash
./dev/build.sh
```

```bash
./dev/patch.sh <name>.patch
```

```bash
npm run watch
```

```bash
./script/code.sh
```

--------------------------------

### Flatpak: Disable Wayland socket for HiDPI blur

Source: https://github.com/vscodium/vscodium/blob/master/docs/troubleshooting.md

Run this command to disable the Wayland socket, which fixes a blurry screen with HiDPI on Wayland.

```bash
flatpak override --user --nosocket=wayland com.vscodium.codium
```

--------------------------------

### Find default file manager with grep

Source: https://github.com/vscodium/vscodium/blob/master/docs/usage.md

Use this command to list file managers associated with the inode/directory MIME type, helping you identify the correct desktop entry to use in mimeapps.list.

```bash
> grep directory /usr/share/applications/mimeinfo.cache
inode/directory=codium.desktop;org.gnome.Nautilus.desktop;
```

--------------------------------

### Manual registry key for VSCodium policy

Source: https://github.com/vscodium/vscodium/blob/master/docs/troubleshooting.md

When setting policies manually via Registry Editor, create the key at this path. The policy name is a subkey with a REG_SZ or REG_DWORD value.

```text
HKLM\SOFTWARE\Policies\VSCodium\VSCodium\<PolicyName>  (REG_SZ or REG_DWORD)
```

--------------------------------

### Semi-Automated Patch Update Process

Source: https://github.com/vscodium/vscodium/blob/master/docs/howto-build.md

Commands to update patches semi-automatically when a patch fails during build.

```bash
./dev/build.sh
```

```bash
./dev/update_patches.sh
```

```bash
npm run watch
```

```bash
./script/code.sh
```

--------------------------------

### Enable key repeat on macOS with defaults

Source: https://github.com/vscodium/vscodium/blob/master/docs/usage.md

Run this command to disable ApplePressAndHoldEnabled for VSCodium, allowing key repeat when holding a key. The defaults path is specific to VSCodium.

```bash
$ defaults write com.vscodium ApplePressAndHoldEnabled -bool false
```

--------------------------------

### Enable Copilot in settings.json

Source: https://github.com/vscodium/vscodium/blob/master/docs/ext-github-copilot.md

Add this setting to your VSCodium settings to enable AI features. Without it, Copilot features remain disabled.

```json
"chat.disableAIFeatures": false,
```

--------------------------------

### createWatcher call with vendorName 'VSCodium'

Source: https://github.com/vscodium/vscodium/blob/master/docs/patches.md

The modified createWatcher() call in VSCodium's fork, passing 'VSCodium' as the vendorName argument. This results in the registry path HKLM\SOFTWARE\Policies\VSCodium\VSCodium\<PolicyName>.

```ts
createWatcher('VSCodium', this.productName, ...)
```

--------------------------------

### Fix font rectangles on Linux

Source: https://github.com/vscodium/vscodium/wiki/Troubleshooting

Clears fontconfig and snap caches, then rebuilds the font cache. Run this when fonts appear as rectangles on Linux.

```bash
rm -rf ~/.cache/fontconfig 
rm -rf ~/snap/codium/common/.cache
fc-cache -r
```

--------------------------------

### Registry path read by @vscode/policy-watcher

Source: https://github.com/vscodium/vscodium/blob/master/docs/patches.md

The registry path that VS Code's policy watcher reads from on Windows. This is the default path that VSCodium replaces.

```text
HKLM\SOFTWARE\Policies\Microsoft\<productName>
```

--------------------------------

### Clear fontconfig cache to fix rectangle fonts

Source: https://github.com/vscodium/vscodium/blob/master/docs/troubleshooting.md

Run these commands to clear font caches and rebuild the font cache, which should resolve fonts showing up as rectangles.

```bash
rm -rf ~/.cache/fontconfig
rm -rf ~/snap/codium/common/.cache
fc-cache -r
```

--------------------------------

### VSCodium GPO registry path

Source: https://github.com/vscodium/vscodium/blob/master/docs/troubleshooting.md

VSCodium reads Group Policy values from this registry path, which differs from VS Code's path. Use this when deploying policies via GPO.

```text
HKLM\SOFTWARE\Policies\VSCodium\VSCodium
```

--------------------------------

### VS Code GPO registry path

Source: https://github.com/vscodium/vscodium/blob/master/docs/troubleshooting.md

VS Code reads policies from this registry path. VSCodium uses a different path, so GPOs configured for VS Code will not affect VSCodium.

```text
HKLM\SOFTWARE\Policies\Microsoft\VSCode
```

--------------------------------

### Fix rendering glitches on Linux (GPU cache)

Source: https://github.com/vscodium/vscodium/wiki/Troubleshooting

Deletes the GPU cache to fix rendering glitches (text or interface not appearing) on Linux. This is a workaround for a Chromium/Electron bug affecting VSCodium versions since 1.82.

```bash
rm -rf ~/.config/VSCodium/GPUCache
```

--------------------------------

### Final Windows registry key for VSCodium policies

Source: https://github.com/vscodium/vscodium/blob/master/docs/patches.md

The final registry path that VSCodium reads policies from, differing from VS Code's path (Microsoft\VSCode). This is the root cause of issue #2714.

```text
HKLM\SOFTWARE\Policies\VSCodium\VSCodium\<PolicyName>
```

--------------------------------

### Remove quarantine attribute on macOS

Source: https://github.com/vscodium/vscodium/wiki/Troubleshooting

Removes the quarantine attribute from VSCodium.app on macOS. Use this to fix the 'VSCodium.app is damaged and can’t be opened' error.

```bash
xattr -r -d com.apple.quarantine /Applications/VSCodium.app
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.