Merged

Language changes reach newly launched desktop apps

dhh proposed and merged omacom/omarchy#15791 into quattro. Switching languages now updates Hyprland's running environment and restarts the desktop shell after the new value is accepted. Apps subsequently opened through shortcuts or the launcher can inherit the selected language without another login.

Reviewer greptile-apps[bot] identified a documentation qualification in omacom/omarchy#15791:discussion_r4305533187: a later uwsm LANG override returns at the next login, but does not survive a live language switch. The change is a development-branch merge, not evidence of a stable release.

Merged

Each monitor gets its own workspace shortcuts

ryanrhughes merged omacom/omarchy#15655 into quattro, giving each monitor local workspaces 1 through 10 and a bar showing its own set. Number shortcuts now act on the focused monitor. Disconnected screens' workspaces merge onto another screen and return when the original monitor reconnects.

After the merge, greptile-apps[bot] flagged monitor identity, stale return records and custom state-directory handling. ryanrhughes then merged omacom/omarchy#15867 to address all three, reporting reproductions and regression tests. Saved layouts remain tied to workspace numbers, and directional shortcuts cannot reach monitors touching only at a corner.

alexgeorgousis explained that assigning apps to fixed workspace shortcuts now requires focusing their monitor first. In omacom/omarchy#15655:issuecomment-6252794912, ryanrhughes suggested custom monitor-specific bindings and said an overview feature was incoming; that response does not establish that the overview has shipped.

Merged

Default command-line tools move to native mise lazy shims

ryanrhughes merged jdx's omacom/omarchy#9596 into quattro. Twenty default tools now use mise's native lazy installation instead of handwritten wrappers that could rewrite configuration on every launch or loop when gh served as mise's credential helper. The migration preserves customized scripts and user-owned symlinks. The change requires mise 2026.10.11.

In background discussion on October 8, charlielockyer-rice reported stale agent clients and confusion over native updaters. jdx responded by adding automatic agent updates. The merged configuration checks the eleven agent CLIs at most every four hours and runs the installed version if an update fails or the machine is offline.

Remove and Restore Preinstalls now control the system defaults per user, while individual tools can be disabled in favor of a user's own installation. The PR reports focused validation, but explicitly leaves fresh ISO installation and the interactive removal and restoration flow needing validation.

Merged

OpenClaw migration fixes preserve updates and user-owned installs

spencerbull merged omacom/omarchy#14212 into quattro, retiring the old OpenClaw migration and introducing a new move to a self-updating user runtime. It fixes checks that failed under the update command's restricted PATH and adds gateway recovery. spencerbull subsequently merged omacom/omarchy#15864, removing the general migration deferral mechanism: without seed files, the move now finishes without moving anything, with launcher recovery handling later setup.

emirb then proposed and merged omacom/omarchy#15875 into quattro. A conflicting user-owned OpenClaw command or gateway now leaves that installation untouched and allows the update to finish. Actual setup failures still leave the migration pending. greptile-apps[bot] reviewed this distinction through code inspection and explicitly reported that it did not run tests.

Separately, spencerbull merged omacom/omarchy-pkgs#797 into master, restoring the seed package and removing OpenClaw from the fast ring. github-actions[bot] reported version 2026.10.4-2 live on edge for both architectures in omacom/omarchy-pkgs#797:issuecomment-6252395093. That publication report establishes edge availability, not a stable release containing the quattro fixes.

Merged

Stable promotion waits for the tested Arch mirror snapshot

emirb proposed and merged omacom/omarchy-pkgs#1247 into master. Stable package promotion now stops unless the stable and release-candidate Arch mirror timestamps match, and also stops if either timestamp cannot be read. The PR describes an 18-minute mismatch during the 4.0.5 rollout that paired Quickshell built for Qt 6.12 with Qt 6.11 and prevented the shell from starting.

Further master commits refined recovery guidance when stable is newer than rc. omacom/omarchy-pkgs@49583e017635 points maintainers to a manual snapshot copy rather than the removed reverse-sync helper. The matching-snapshot guard remains; aarch64 has no equivalent check because its channels use the live Arch Linux ARM mirror.

Committed

Boot-image guard protects passphrase entry with non-Latin layouts

The quattro commit associated with kevincardwell, attributed to Kevin Cardwell, restores protection against a non-Latin console layout reaching the Plymouth disk-unlock prompt. omacom/omarchy@1d134a5261cb explains that Arch's Plymouth hook began copying the console configuration independently, bypassing Omarchy's existing exclusion and potentially making a LUKS passphrase impossible to type.

The guard excludes that copy for the listed non-Latin layouts while preserving Latin layouts on older configurations. A migration rebuilds affected boot images. This is a committed change on quattro; the supplied record does not establish stable availability.

Committed

Package retirement can target obsolete channels and architectures

Master commits expand package retirement beyond recipes that have disappeared entirely. The earlier change associated with ryanrhughes, omacom/omarchy-pkgs@7c764cfb4bde, allows retiring an architecture a recipe no longer builds, addressing old x86_64 Pinta packages that shadow Arch's newer version.

emirb's omacom/omarchy-pkgs@56689c7d0d75 extends the decision to individual channels. Its stated case is obsolete development packages on stable that can derail switching from edge to stable. The planner also matches package bases to their actual recipes. omacom/omarchy-pkgs@d3995e0bef27 makes unreadable recipes stop planning entirely, preventing a read failure from being mistaken for a removed package. These commits change retirement tooling; they do not establish that the obsolete entries were removed.