Understand why a git-installed theme leaves Neovim and terminals unthemed
The cause is confirmed in detail. bin/omarchy-theme-set defines INSTALLED_THEME_DENIED=(alacritty.toml foot.ini ghostty.conf kitty.conf vscode.json), is_denied_installed_file additionally returns true for every *.lua, and theme_came_from_a_repo gates it on a .git directory. The in-source comment even says a repo theme 'cannot supply Lua, a terminal config, or vscode.json'. The user-template path ~/.config/omarchy/themed is confirmed in omarchy-theme-set-templates and docs/theming.md ('User templates in ~/.config/omarchy/themed/*.tpl are processed before the built-in templates'). One factual error: bin/omarchy-theme-update takes NO argument. It iterates omarchy-theme-extras and git-pulls every user-installed git theme, so omarchy theme update <name> silently ignores the name.
The stripping is a deliberate security boundary: installed themes must not be able to run code. Do not defeat it by hand-copying .lua files out of a stranger's theme repo into your nvim config without reading them first.
Symptom
You install a community theme with omarchy theme install <git-url>, and the bar, terminal palette and shell surfaces follow it, but Neovim keeps its stock colorscheme, terminal niceties like inactive border colors are generic, and VS Code is unstyled. omarchy theme update appears to succeed but nothing on the desktop changes.
Cause
Deliberate, as of commit ef6d9e6 / PR #7884 ("Stop an installed theme from running code", shipped in 4.0.0.r1803). omarchy-theme-set now drops every .lua, terminal config (kitty.conf, foot.ini, ghostty.conf, alacritty.toml) and vscode.json from themes installed from a git repo, then regenerates them from $OMARCHY_PATH/default/themed/*.tpl. So a repo theme cannot ship a Neovim integration at all. Separately, omarchy theme update only runs git pull inside the clone and never re-stages, so pulled changes stay invisible until you re-select the theme, and when the re-stage happens, the same files are stripped again.
Fix
omarchy-theme-update takes **no arguments**. It git-pulls every user-installed git theme (those listed by omarchy-theme-extras). Passing a name is silently ignored. Force the pulled theme to actually re-stage:
omarchy theme update # pulls ALL git themes
omarchy theme set <name> # re-stage; theme update alone never re-stages
The stripping is deliberate and confirmed in bin/omarchy-theme-set: every *.lua plus INSTALLED_THEME_DENIED=(alacritty.toml foot.ini ghostty.conf kitty.conf vscode.json) is dropped from any theme with a .git directory, then regenerated from $OMARCHY_PATH/default/themed/*.tpl. Dropped files are named on stderr, so watch that output:
omarchy theme set <name> 2>&1 | grep -i ignored
For the Neovim colours the author intended, install their colorscheme plugin yourself. In ~/.config/nvim/lua/plugins/theme.lua:
return {
{ "tahadx/noir.nvim", lazy = false, priority = 1000 },
{ "LazyVim/LazyVim", opts = { colorscheme = "noir" } },
}
then inside nvim: :Lazy sync
For terminal details the stock template does not cover, put your own template in the user templates directory. These are processed *before* the built-ins, and a user template sharing an output filename causes the built-in to be skipped entirely:
mkdir -p ~/.config/omarchy/themed
# e.g. ~/.config/omarchy/themed/kitty.conf.tpl
omarchy theme refresh
Verify
omarchy theme set <name> then ls ~/.local/state/omarchy/current/theme/ shows regenerated kitty.conf/foot.ini, and nvim opens with the colorscheme you installed rather than the LazyVim default.