Fix the autogenerated-config banner and lost Omarchy look after an update
The diagnosis is real and the cited issue is genuine: omarchy #5797 'Omarchy 3.8.0 breaks hyprland' says exactly this: 3.8.0 shipped Lua configs for 0.55 while the stable mirror still pointed at 0.54.3, producing the autogenerated-config banner. The reporter's own workaround was omarchy refresh pacman edge + reboot. omarchy-channel-current and omarchy-channel-set both exist in bin/ and omarchy-channel-set carries omarchy:requires-sudo=true, so the sudo is right. Two problems. First, this is a May 2026 skew that stable resolved long ago. On any current system the first move is omarchy-update, not a channel switch. Second, and more serious, the record understates what a channel switch does: I read bin/omarchy-channel-set, and 'edge' does not merely repoint a mirror, it swaps the installed packages to omarchy-dev + omarchy-settings-dev. Going back with omarchy-channel-set stable swaps them back AND returns the pacman mirror to stable, which means Hyprland gets downgraded. That reintroduces the exact 0.54-can't-parse-Lua breakage if stable has not actually caught up yet. 'Once stable catches up, move back' needs to be a hard precondition, not an afterthought.
Switching to edge or dev pulls less-tested packages system-wide, not just Hyprland. dev links Omarchy to a git checkout in ~/omarchy and is for Omarchy developers only. Never mix mirrors by hand. That is how you get a partial upgrade.
Symptom
After updating Omarchy 3.7.0 -> 3.8.0 and rebooting, Hyprland comes up with the yellow 'autogenerated config' banner and none of the Omarchy look, keybindings or window rules apply.
Cause
Omarchy 3.8.0 shipped the new Hyprland 0.55 Lua configs, but the Omarchy stable pacman mirror was still pinned to hyprland 0.54.3. A 0.54 binary cannot parse hyprland.lua, finds no usable config, and falls back to its own autogenerated one. It is a channel/version skew, not a broken config.
Fix
Diagnose first. This is almost always already fixed:
hyprctl version | head -1
pacman -Q hyprland
omarchy-channel-current
omarchy-update # try this FIRST; stable has long since caught up
Only if omarchy-update genuinely leaves you with Lua configs and a pre-0.55 Hyprland is a channel switch warranted. Understand what it does: omarchy-channel-set edge replaces the omarchy/omarchy-settings packages with omarchy-dev/omarchy-settings-dev and moves you to the edge repo. It is a package swap, not a mirror tweak.
sudo omarchy-channel-set edge
reboot
Before going back, CHECK that stable actually carries a Hyprland new enough for the configs you have, or you will downgrade Hyprland straight back into the same breakage:
omarchy-channel-current
# verify stable's hyprland >= the version your configs need, THEN:
sudo omarchy-channel-set stable
reboot
omarchy-refresh-hyprland restores ~/.config/hypr/*.lua from the shipped defaults and backs yours up as *.bak.<epoch> (verified in bin/omarchy-refresh-config), but it will not help if the installed Hyprland cannot parse Lua at all.
Verify
hyprctl version reports >= 0.55.0, the autogenerated banner is gone, and your Omarchy keybindings (SUPER+Return etc.) work.