02Fast-ring packages face checks against older channel libraries
dhh merged omacom/omarchy-pkgs#904 into master, adding checks intended to stop an edge-built fast-ring package from reaching rc or stable with incompatible dependencies. The check compares library and dependency availability across channels and rejects Python modules and locally compiled Qt or libpython packages from the fast ring. On aarch64, which uses live Arch Linux ARM repositories across channels, only the eligibility rules are checked.
The change removes ten packages from the ring and adds 25 eligible packages. 
github-actions[bot] reported successful publication of listed artifacts to edge, rc and stable in omacom/omarchy-pkgs#904:issuecomment-6158595832, while also noting that some planned slots did not run after an earlier failure. This is package-channel publication, separate from an Omarchy stable release.
03Kimi joins the coding-agent picker and usage panel
dhh merged 
sorenmat's Kimi picker proposal, omacom/omarchy#7261, into quattro. Kimi installs through mise and can become the default coding agent. The separate committed collector, omacom/omarchy@c88e7dd566ab, adds weekly quota and session limits to the agents panel, with credential refresh handling and protection against assigning cached limits to a different account.
Before the picker merge, 
omarchybot reported revising provisioning and Refresh Applications to recreate every mise wrapper consistently, including Kimi, Cursor CLI and Muse. Automatic Kimi migration and removal retain protection for independently installed commands. These changes are development-branch additions.
04Agent subscription logins can be copied between machines
dhh opened and merged omacom/omarchy#15405 into quattro on October 14. It adds an SSH command for copying all or selected agent account logins, reducing repeated sign-ins when setting up another machine. Both machines need the command installed.
The current description says imports preserve destination credentials and preferences by default, with explicit replacement available after matching sessions close. It also describes complete-stream validation, rollback and interrupted-import recovery. Validation used fixture credentials and simulated SSH; the supplied record does not establish a transfer of personal credentials to another machine.
05Quiet boot defaults shorten the Limine menu wait
dhh merged omacom/omarchy#15301 into quattro, introducing a one-second quiet Limine default and a System menu action for returning to the boot menu. Existing explicit timeout settings are preserved during migration, and any key can reveal the normally hidden menu.
In October 13 background review, 
greptile-apps[bot] requested coverage for denied authentication. dhh reported adding a case that leaves the menu untouched when authorization fails; the committed change also keeps that migration pending. The current PR description records a correction to the reboot action so the requested menu remains visible instead of counting down while hidden, and says a real reboot check still needs a person.
06Fingerprint verification rests while lock-screen displays are blank
dhh merged omacom/omarchy#15294 into quattro on October 14. Blanking the lock screen now holds back new fingerprint attempts while allowing an attempt already running to finish. Input, a detected resume or an arriving display can restart verification. Users must wake a blank screen before unlocking with a finger.
In October 13 background review, greptile-apps[bot] identified a wake path that could shorten the quiet period needed by a failing reader. On October 14, dhh reported preserving the backoff tier independently of the remaining timer, with a regression check. The committed change retains that fix. The current description still documents a limitation when brightness or volume bindings wake a display without sending input to the lock.
07Links opened by apps bring the receiving browser window forward
The quattro commit omacom/omarchy@9f49906d2241, authored by dhh, routes HTTP and HTTPS links through Omarchy's browser launcher. It addresses desktop-portal launches from apps such as Electron clients where a new tab reached the browser but its window stayed hidden. When several windows match, the launcher focuses the one used most recently.
The change also suppresses browser default-handler prompts that would otherwise appear because Omarchy's routing entry sits in front of the browser. This is a committed development-branch change.
08Power profiles gain hardware-specific behavior for NVIDIA and Snapdragon
Two master commits in omarchy-pkgs are attributed to 
ryanrhughes. omacom/omarchy-pkgs@0f3d0404a900 replaces Omarchy's CPPC driver with NVIDIA's RTX Spark driver to address desktop lag on N1x hardware. Its governor selection varies with power profile and power source, and its hardware probe is restricted to processors reporting NVIDIA RTX Spark.
omacom/omarchy-pkgs@3280e02b7d5e adds a generic cpufreq driver and Snapdragon X frequency caps: 60 percent in power-saver, 75 percent in balanced and no cap in performance. The commit reports Surface Pro 11 validation and caps lifting when the daemon stops; those results are contributor-reported measurements.
09N1x dock fixes target dark displays and incorrect lid behavior
ryanrhughes opened and merged omacom/omarchy-pkgs#1100 into the n1x development branch. Its kernel changes retain dock tunnels through suspend and space out DisplayPort tunnel teardown when unplugging a dock. An NVIDIA driver patch reports USB-C displays as DisplayPort so logind recognizes the docked configuration when the lid closes.
ryanrhughes reported successful suspend and unplug checks on a ProArt P14 with a CalDigit TS4 and two displays. An accompanying Aquamarine patch handles connectors that gain modes late, but that case had not occurred during the reported testing. This merge establishes n1x branch integration.
10ARM image builds standardize on linux-omarchy
The quattro commit omacom/omarchy-iso@62d151d4d162, authored by 
emirb, makes linux-omarchy the only accepted kernel for aarch64 image builds. It removes the alternative Arch Linux ARM kernel path and its associated console, compression and device-tree handling.
The installer continues to install the kernel recorded by the image. The supplied event establishes a committed image-build change, rather than a released installation image.
11Memory watchdog proposal separates deterministic protection from an agent responder
KewkLW narrowed the still-open omacom/omarchy#15272 to an optional watchdog that warns about memory pressure, identifies apps killed by systemd-oomd and pauses eligible work before the kill threshold. In October 13 background discussion, 
jandrusk recommended separating those functions from a headless agent capable of killing processes. KewkLW confirmed that split on October 14, removing the responder from this branch.
A later October 14 update added sustained-stall triggers, a five-minute hold-off after users resume work, enablement checks and stronger pause-record handling. Pausing stops further growth without freeing memory. The current description, edited after coverage, continues to describe an off-by-default proposal and says an end-to-end graphical session check has not been run.
12Shell accessibility proposal returns for review after a rebase
calebl's omacom/omarchy#13212 remains open. It proposes accessible roles, names, states and actions for shared shell controls so assistive technology can discover and operate them. Its current description requires Quickshell's accessibility-tree fix, included in version 0.3.2 and later.
In October 13 background discussion, 
monsieur-mouton described the unreadable shell as a barrier to moving to Omarchy and requested a rebase. On October 14, monsieur-mouton reported that the branch was rebased and mergeable and offered to test it with Orca. That is progress toward review, rather than evidence of a merged accessibility feature or completed screen-reader testing.
