Fix VS Code losing its color theme when you use a community Omarchy theme
The staging half is correct: vscode.json is on INSTALLED_THEME_DENIED in bin/omarchy-theme-set and is dropped from any theme directory containing .git, which is what omarchy theme install leaves, so ~/.local/state/omarchy/current/theme/vscode.json is genuinely absent. The four toggle flag names are exact (skip-vscode-theme-changes, skip-vscode-insiders-theme-changes, skip-codium-theme-changes, skip-cursor-theme-changes), omarchy-toggle <flag> on and the verbless flip are correct, and the settings paths match. But the symptom and cause are wrong about the consequence. set_theme() in bin/omarchy-theme-set-vscode has an intermediate branch the record skips: elif [[ -f $GENERATED_THEME ]] where GENERATED_THEME is ~/.local/state/omarchy/current/theme/vscode-theme.json, and default/themed/vscode-theme.json.tpl exists, so that file is generated for every theme that has a colors.toml (which a cloned theme IS allowed to ship, and which is even synthesized from alacritty.toml when absent). In that branch the script installs the local local.omarchy-theme extension and sets workbench.colorTheme to "Omarchy". So VS Code does retint after installing a cloned theme. It does so with Omarchy's mechanically generated palette rather than the author's chosen extension. The elif [[ -f $settings_path ]] branch that seds the key out is reached only when there is neither vscode.json nor vscode-theme.json, i.e. a theme with no colors.toml at all. That, not the vscode.json denial, is what drops the editor to Dark+.
Removing .git promotes the whole cloned tree to a hand-written theme, so Omarchy will then stage and act on every file in it. hyprland.lua and gum_env.lua are executed by Hyprland at login, neovim.lua by Neovim at startup, the terminal configs name the program your terminal launches, and vscode.json causes an extension to be installed. Read those files before doing it. It also breaks omarchy theme update for that theme.
Symptom
Every stock theme retints VS Code, VSCodium or Cursor, but a theme installed with omarchy theme install does not. Worse, VS Code drops back to Dark+ entirely because "workbench.colorTheme" has been removed from settings.json. ls ~/.local/state/omarchy/current/theme/vscode.json says No such file or directory, even though the theme's repo obviously contains one.
Cause
vscode.json names an extension that bin/omarchy-theme-set-vscode would install with --install-extension, and a VS Code extension is arbitrary JavaScript, so it sits on INSTALLED_THEME_DENIED in bin/omarchy-theme-set alongside alacritty.toml, foot.ini, ghostty.conf, kitty.conf and every *.lua, and is dropped from any theme whose directory contains a .git. That is exactly what omarchy theme install leaves behind. What you get instead is Omarchy's own generated theme: set_theme() falls to its elif [[ -f $GENERATED_THEME ]] branch, renders default/themed/vscode-theme.json.tpl into the staged theme, registers it as the local extension local.omarchy-theme, and writes "workbench.colorTheme": "Omarchy". So the editor still retints, just with a mechanical palette instead of the author's hand-tuned extension theme. The key is stripped out of settings.json entirely, dropping the editor to Dark+, only in the last branch, when neither vscode.json nor the generated vscode-theme.json exists, which means the theme shipped no colors.toml either (and none could be derived from an alacritty.toml).
Fix
First find out which of the two situations you are in:
ls ~/.local/state/omarchy/current/theme/vscode.json ~/.local/state/omarchy/current/theme/vscode-theme.json
grep -n 'workbench.colorTheme' ~/.config/Code/User/settings.json
If vscode-theme.json exists, VS Code is on the generated "Omarchy" theme. To get the author's theme instead, install it yourself and pin it:
jq -r '.name, .extension' ~/.config/omarchy/themes/<name>/vscode.json
code --install-extension <publisher.extension>
omarchy-toggle-enabled skip-vscode-theme-changes && echo already-set || echo not-set
omarchy-toggle skip-vscode-theme-changes on
then set "workbench.colorTheme": "<Theme Name>" in ~/.config/Code/User/settings.json.
If BOTH files are missing, the theme has no colors.toml and that is why the key was deleted. Give it one and the generated theme comes back:
cp /usr/share/omarchy/themes/tokyo-night/colors.toml ~/.config/omarchy/themes/<name>/colors.toml
omarchy theme set <name>
The re-file-as-your-own escape hatch is correct as written (a plain directory with no .git is staged in full, vscode.json included).
Verify
ls ~/.local/state/omarchy/current/theme/vscode.json exists (or the toggle is set), grep colorTheme ~/.config/Code/User/settings.json still shows a theme name after omarchy theme set <name>, and VS Code opens in the expected colours.