dhh proposed and merged two safeguards into the quattro development branch. omacom/omarchy#17524 restarts the shell before pending migrations so newly added IPC functions are available, preventing a stale shell from repeatedly blocking the migration queue. omacom/omarchy#17553 prevents a running Hyprland whose binary was replaced during an update from reloading configuration intended for its replacement. Reloads remain disabled and errors hidden until the session restarts.
greptile-apps[bot] identified a test that could pass with migrations running before the restart. dhh responded that the revised test records the pending check separately and covers the no-pending-work case. These are development merges.
The quattro commit omacom/omarchy@cfd8106faaac, with 
scottjones listed as a participant and Scott Jones as its attributed author, disables animations, blur and shadows by default when Mesa reports software rendering on Hyprland's rendering device. The change targets sessions where drawing every frame on the CPU causes stutter and sustained CPU work.
The final implementation allows the animations toggle to override that default across sessions, respects user configuration and checks actual effect settings before claiming they were disabled. Its notice appears once per machine and is suppressed where animations were already disabled by choice.
ThePrimeagen opened omacom/omarchy#17588, which remains an open proposal for quattro. It would derive whether a built-in is replaced from installed, enabled clones instead of retaining replacement records that can leave menus or emoji shortcuts disabled after a clone disappears. Enabling another clone would retire its siblings, while switching back would preserve their bar slots and settings.
ThePrimeagen's responses describe fixes for migration recovery and for one restored slot erasing another. The final greptile-apps[bot] summary says the earlier slot-loss problem was fixed. A remaining limitation is explicit: a clone renamed outside the usual naming pattern and deleted before upgrading may leave its built-in disabled because its original relationship can no longer be recovered.
dhh's open omacom/omarchy#17560 proposes daily spending bars for the last 30 days, replacing manual funding configuration for Fireworks and DeepSeek. Fireworks and qualifying OpenRouter accounts use provider activity; other supported views estimate spending from costs saved by pi and opencode on the local machine. Fireworks accounts with monthly caps would instead show a calendar-month meter.
greptile-apps[bot] identified a case where unreadable Fireworks amounts could overwrite valid spending figures with fresh zeros. The review requested preserving the last good result as stale. The supplied proposal remains open, and its local estimates exclude harnesses that do not save per-reply costs.
lbssousa opened the draft proposal omacom/omarchy#17502 to replace GNOME Keyring with oo7. It would seal a per-user unlocking secret through systemd credentials, redirect the Secret portal and migrate existing collections, with rollback if keyring repair or the package transaction fails.
The proposal depends on another repair change, a package dependency adjustment and oo7 0.7 stable reaching Arch. lbssousa explicitly says retained plaintext keyrings and backups mean this would not yet deliver encryption at rest. Reported VM checks cover several login arrangements, but the full pre-Quattro upgrade, fresh installation and aarch64 remain untested.
Opened on October 28, 
T3lluz's omacom/omarchy#16956 remains an open proposal for categories, favorites, recents, remembered skin tones, ranked search and copying without pasting. Its current description also expands the emoji catalog with Unicode names and tone variants.
On November 4, responses posted by T3lluz and explicitly marked as Claude Code acting on the author's behalf described adaptive grid columns and a correction to the preference test's IPC arguments. greptile-apps[bot] accepted the revised width calculation, agreeing that the four-column minimum was reasonable. This advances the proposal's usability and validation without establishing a merge.
spaghetticodez added a KeePassXC report to the still-open omacom/omarchy#16518, citing stable version 2.7.12-5 against Arch's 2.8.0-3 and describing browser-integration and database-import security fixes. These are the contributor's reported package observations, not independently verified mirror measurements.
The thread began on October 24 with 
xsi-dbachmann's report about Brotli and Node.js security updates missing from stable. The November 4 comment expands the reported exposure to a password manager; the supplied records do not establish a subsequent mirror update.
Master commits attributed to Emir Beganovic, with 
emirb listed as a participant, strengthen checks on Omarchy packages that take precedence over Arch packages. omacom/omarchy-pkgs@3e5aeb9e6fd1 requires an explicit list of intentional x86_64 replacements and rejects unlisted ones. omacom/omarchy-pkgs@472b7f0ebc58 excludes aarch64-only recipes from that comparison and includes Arch's core repository.
omacom/omarchy-pkgs@9b527ab5f14a scopes ordinary PR checks to changed recipes while retaining whole-tree daily checks. omacom/omarchy-pkgs@aaff66e98b18 distinguishes actual findings from setup failures so mirror outages do not produce misleading package-lag alerts.
The marketplace main-branch commit omacom/omarchy-plugin-marketplace@cc3e7a2b672f, with 
OnurByte listed as a participant, makes standard-installation approval use the actual matching label-event time. It shares the listing-approval transition and timestamp checks while keeping the two approval labels distinct.
Subsequent commits attributed to 
github-actions[bot] enabled standard installation for io.github.onurbyte.omamonero and emrgim.cycle. The supplied records establish those catalog changes without supplying further details about either plugin's functionality.
