Get back to the stable update channel after dev broke the desktop
The four channels are real and confirmed by manual/30-updates.md, and omarchy-channel-set is correct. But most of the commands are wrong for current Omarchy. omarchy-branch-set DOES NOT EXIST. There is no such file in bin/ (only omarchy-channel-set, omarchy-channel-current, omarchy-version-branch, omarchy-version-channel). Channel and branch are no longer set independently: omarchy-channel-set handles the package repo and the dev checkout together. The dev checkout is at ~/omarchy, not ~/.local/share/omarchy. The manual says 'the dev channel, which links Omarchy directly to a git checkout of the source code in ~/omarchy', so every git -C ~/.local/share/omarchy ... command targets a directory that does not exist on Omarchy 4. omarchy-channel-set stable already ends by running omarchy-update -y, so the trailing omarchy update is redundant. sudo pacman -Syyuu is blocked by the update guard, and the downgrade is already performed for you by omarchy-refresh-pacman. Finally, channel repos are configured from default/pacman/pacman-{stable,rc,edge}.conf, so grepping /etc/pacman.d/mirrorlist is the wrong file.
Downgrading from edge/dev to stable with pacman -Syyuu rolls packages backwards. A downgraded kernel plus an already-rebuilt DKMS module can break the next boot. Take a snapshot (omarchy-snapshot create) before switching channels.
Symptom
User switched to the dev or edge update channel (or a feature branch) to try something new, and now every omarchy update pulls half-finished code: the shell crashes, the menu is broken, or migrations fail. They want back on stable but don't know how.
Cause
Omarchy has four update channels: **stable** (default, packages roughly a month behind), **edge** (latest packages, stable Omarchy code), **rc** (pre-release validation) and **dev** (cutting-edge code *and* packages). dev is explicitly for experienced users and regularly ships breakage. omarchy-channel-set is the single entry point. There is no omarchy-branch-set, and the channel and the source checkout are not set independently: omarchy-channel-set moves the package repo and the dev checkout together, and on dev that checkout is at ~/omarchy.
Fix
Check what you are actually on first:
omarchy-channel-current
omarchy-version-channel
Switch back through the menu, Super + Space > **Setup** > **Channel** > *stable*, or from a terminal. One command does everything: it repoints the pacman channel, swaps the omarchy-dev packages back to the stable ones, unlinks any dev checkout, and finishes by running the update itself:
omarchy-channel-set stable
Do not look for omarchy-branch-set. It no longer exists. Channel and branch are not set independently any more. omarchy-channel-set handles both.
Moving from dev/edge back to stable means *downgrading* packages. omarchy-channel-set already does this for you via omarchy-refresh-pacman, which runs a full pacman -Syyuu with the update guard bypassed. Do not run a bare sudo pacman -Syyuu yourself, because Omarchy's ALPM guard will abort it.
If you had actually been on the **dev** channel, the source checkout lives at ~/omarchy (not ~/.local/share/omarchy). If local edits there are getting in the way, deal with them before switching:
git -C ~/omarchy status
git -C ~/omarchy stash
Switching to stable unlinks that checkout automatically (omarchy-dev-unlink), leaving OMARCHY_PATH back at /usr/share/omarchy. A reboot is flagged as required. Take it.
If the system is still inconsistent afterwards, the documented reset reinstalls the default packages, forces stable, downgrades anything too new, and rewrites every config file:
omarchy reinstall
Verify
git -C ~/.local/share/omarchy branch --show-current shows the stable branch, /etc/pacman.d/mirrorlist points at the stable Omarchy mirror, and omarchy update completes cleanly.