Uninstall VSCodium on Mac

Save projects, finish integrated-terminal tasks, and back up editor configuration before quitting VSCodium and moving it from Applications to the Trash. Settings and extensions need separate backups: settings live in ~/Library/Application Support/VSCodium/User, extensions in ~/.vscode-oss. These steps cover the download from vscodium.com and the Homebrew cask.

Locate the actual configuration

Open the user settings JSON from the command palette and use its displayed file location to find and copy the configuration directory. For a standard install that is ~/Library/Application Support/VSCodium/User, which holds settings.json, key bindings, and snippets. Respect custom user-data locations or portable mode, which keeps data in a codium-portable-data folder instead (VSCodium usage). The ~/.vscode-oss directory mainly holds extensions; copying it alone does not back up user settings. VSCodium documentation

Remove the app

Quit VSCodium and move it from Applications to the Trash. If you installed the codium command with Shell command: Install 'codium' command in PATH, check it afterward with the commands below.

Where VSCodium keeps its files

Check the result

pgrep -il vscodium
command -v codium
ls -d ~/Library/Application\ Support/VSCodium ~/.vscode-oss ~/.vscode-oss-shared

No output from pgrep means VSCodium has quit. If command -v codium prints a path, inspect which app or installation channel it targets before removing a stale entry; no output only means the current PATH cannot find it. For ls, No such file or directory means that folder is gone; a listed path is still on disk, which is expected for anything you kept. Afterward, confirm retained projects still open.

If you installed it with Homebrew

Mole skips --zap when its list reaches unchecked or shared data, or cannot be fully checked, and still cleans the leftovers you selected.

Running brew uninstall --cask --zap vscodium yourself runs the zap list regardless of which rows you check in Mole. It trashes ~/.vscode-oss (your extensions) and ~/Library/Application Support/VSCodium (your settings, key bindings, and snippets), along with caches, preferences, and saved state. Back up the User folder first, or run brew uninstall --cask vscodium without zap to keep them. The zap list does not include ~/.vscode-oss-shared.

Why VS Code settings did not appear

VSCodium and VS Code do not use the same user-data set. Locate the settings JSON actually used by VSCodium from its command palette, then back it up separately from extensions in ~/.vscode-oss. Copying VS Code's ~/.vscode alone does not establish that VSCodium settings and extensions were saved. Keep VS Code's own configuration when VS Code is still installed. Removing VS Code itself is covered in Uninstall VS Code on Mac Without Losing Settings.

What Mole lists

The unselected data rows below assume Remove data and settings with apps is off, the default. Turning it on can select eligible app-owned review rows; keep wanted data unchecked. Shared stores and protected data retain individual review or protection.

For VSCodium downloaded from vscodium.com:

Mole does not list ~/.vscode or ~/Library/Application Support/Code. Those belong to Visual Studio Code.

What this test covered

VSCodium was installed from the Homebrew cask on September 17, 2026 and uninstalled through Mole, which ran the zap list. The zap step removed ~/.vscode-oss before Mole reached it, and ~/.vscode-oss-shared, created at first launch, stayed because Mole did not list it then. On September 26, 2026, VSCodium 1.135 from its official GitHub download was installed again and removed with a development build of Mole with every row ticked: the app and 12 listed items went to the Trash, including the 17 MB Application Support/VSCodium, and nothing from the list remained. Visual Studio Code's ~/.vscode and Code folders on the same Mac were untouched. Portable mode and the codium command were not tested.