Stop omarchy update wiping your config edits every time
The principle (never edit Omarchy's defaults, put overrides in the user layer) is correct and still correct. But essentially every specific in this record is obsolete, and the quoted load order is not real. Verified: config/hypr/hyprland.conf DOES NOT EXIST in the current repo, so the quoted source = block cannot be reproduced from upstream. Current Omarchy uses Lua: ~/.config/hypr/hyprland.lua does dofile(OMARCHY_PATH .. "/default/hypr/bootstrap.lua"), then require("default.hypr.omarchy"), then requires hypr.monitors / hypr.input / hypr.bindings / hypr.looknfeel / hypr.autostart, then default.hypr.toggles. The defaults path is /usr/share/omarchy (pacman-owned), not a git checkout at ~/.local/share/omarchy, so the reason edits vanish is that a package upgrade overwrites them, not a git hard-sync. The unbind = SUPER, K conf syntax no longer applies. Omarchy 4 exposes omarchy_default_bindings = false and omarchy_preinstalled_bindings = false in hyprland.lua and uses o.bind(...).
Symptom
User edits a config file, everything works, then the next omarchy update silently reverts all of it. They report "my keybindings/theme tweaks keep getting wiped on every update." Usually they had edited something under ~/.local/share/omarchy/default/hypr/.
Cause
Omarchy 4's defaults are pacman-owned and live at /usr/share/omarchy (the omarchy package). Edits there vanish because a package upgrade rewrites the files, not because of a git hard-sync. The ~/.local/share/omarchy git checkout was Omarchy 3. The config is Lua and layered: ~/.config/hypr/hyprland.lua does dofile(OMARCHY_PATH .. "/default/hypr/bootstrap.lua"), then require("default.hypr.omarchy"), then requires hypr.monitors / hypr.input / hypr.bindings / hypr.looknfeel / hypr.autostart, then default.hypr.toggles. The user files are loaded after the defaults so they win. Editing the defaults is always the wrong layer.
Fix
Never edit anything under /usr/share/omarchy (older installs: ~/.local/share/omarchy). On current Omarchy that directory is owned by the omarchy pacman package, so every upgrade overwrites it. Put overrides in the matching user file, because they are loaded after Omarchy's defaults and therefore win:
| Want to change | Edit | |---|---| | monitors, scale, GDK_SCALE | ~/.config/hypr/monitors.lua | | keyboard layout, repeat, touchpad | ~/.config/hypr/input.lua | | keybindings | ~/.config/hypr/bindings.lua | | gaps, borders, animations, blur | ~/.config/hypr/looknfeel.lua | | apps started at login | ~/.config/hypr/autostart.lua |
The real load order lives in ~/.config/hypr/hyprland.lua:
-- Omarchy's bootstrap keeps path setup out of this user config.
dofile((os.getenv("OMARCHY_PATH") or "/usr/share/omarchy") .. "/default/hypr/bootstrap.lua")
-- Load Omarchy defaults.
require("default.hypr.omarchy")
-- Your personal overrides, loaded after the defaults so they win.
require("hypr.monitors")
require("hypr.input")
require("hypr.bindings")
require("hypr.looknfeel")
require("hypr.autostart")
require("default.hypr.toggles")
To replace a default keybinding, just bind the same key in ~/.config/hypr/bindings.lua, which is loaded later and overrides:
o.bind("SUPER + K", "My command", "your-command")
To turn Omarchy's bindings off wholesale, uncomment the flags in hyprland.lua:
omarchy_default_bindings = false -- drop all Omarchy bindings
omarchy_preinstalled_bindings = false -- keep window-manager bindings, drop app launchers
Apply without logging out:
hyprctl reload
On an older Omarchy 3 install the same principle holds, but the files are .conf, the defaults live in ~/.local/share/omarchy/default/hypr/, and unbinding uses unbind = SUPER, K.
Verify
hyprctl binds | grep -i <yourkey> shows your binding, and it survives the next omarchy update.