Merged

App icon styles become independent of theme colors

dhh proposed and merged omacom/omarchy#18879 into the quattro development branch. Launcher and dock icons now come from a separately selected set: Papercraft, pixel-art Arcade, or Original for applications' own icons. Themes supply colors, while custom sets can override individual drawings. Theme-local icon directories are no longer read.

The committed implementation protects concurrent selections and refuses to replace custom sets containing local work. dhh also reported fixing removal so it cannot erase a newer selection. A follow-up committed a visual picker with generated previews that refresh when icons or colors change, and another extended both built-in sets to additional applications. These changes are recorded in omacom/omarchy@dc49cec0fd9b, omacom/omarchy@1699ae775b8d and omacom/omarchy@6a46afbc711e.

Merged

Omaview and Files take over media viewing and file dialogs

dhh proposed and merged omacom/omarchy#19034 and omacom/omarchy#19035 into quattro. Omaview becomes one Media Viewer for supported pictures, videos and music, including finished recordings and downloads. The migration removes imv and mpv-mpris; mpv remains because the wallpaper engine needs it. The PR explicitly leaves real-desktop verification of the replacement webcam overlay and warning sound outstanding.

Files becomes the preferred Open and Save dialog through Folio's portal backend, with GTK as fallback. greptile-apps[bot] identified that the migration could replace a linked configuration with a regular file; dhh reported changing it to edit through the link. Supporting Omaview and Folio 0.5.0 packaging was committed on the package repository's master branch in omacom/omarchy-pkgs@4cdd0a9be818 and omacom/omarchy-pkgs@3c4bee488244.

Merged

Agent setup shows downloads before browser login

dhh proposed and merged omacom/omarchy#19002 into quattro to address first sign-ins that appeared stuck while an agent CLI downloaded silently. Setup now shows installation progress before browser login, adds Claude Code, Codex and Grok Build launchers after sign-in, and announces when an agent or local model is ready. Existing signed-in agents receive launchers through a migration.

Review changed cancellation and quota handling. greptile-apps[bot] warned that Cancel left downloads running and that unreadable Grok monthly usage could become a misleading zero. dhh reported fixes that interrupt downloads and restrict the weekly fallback to accounts whose monthly quota is zero; other unreadable monthly replies retain the previous figures marked stale.

Open proposals

An opt-in systemd-boot switch proposes snapshot-aware recovery

omarchybot opened omacom/omarchy#18974, which remains an open proposal targeting quattro. It would offer eligible x86 UEFI installations a staged switch from Limine to systemd-boot, preserving snapshot boot and restore through stored boot images and signed UKI profiles. Secure Boot itself is explicitly outside this proposal.

The proposed switch trials systemd-boot once while retaining Limine as the firmware default, promotes it after a successful boot, and removes Limine only after another boot confirms the new order. Earlier snapshots would remain on disk but could not boot or restore through systemd-boot. ARM, BIOS installations and fresh ISO installs would retain Limine. The proposal reports QEMU testing; those results are the submitter's account.

Merged

N1x installation moves NVIDIA preparation into image builds

dhh proposed and merged omacom/omarchy-iso#445 into quattro. It packs the N1x NVIDIA stack into a platform layer during image construction and extracts it after writing the generic root image, avoiding package preparation on the freshly installed disk. Older images without a layer retain the previous installation path. The proposal's extraction-time expectation had not yet been verified on hardware.

greptile-apps[bot] found that verification could miss a stalled layer read. dhh reported extending progress accounting, stall detection and timeout sizing to include the layer before merging. Separately, dhh merged omacom/omarchy#19022 into quattro to build the first-install ARM keyring alongside system setup, with finalization waiting or rebuilding on failure. The committed omacom/omarchy@b80cf8e09707 also removes the N1x rescue boot entry and its fallback image, whose build the commit describes as taking about a minute.

Merged

Snapdragon firmware coverage expands across more machines

birkskyum proposed twelve OEM firmware packages covering thirteen Snapdragon machines in omacom/omarchy-pkgs#2781, and ryanrhughes merged them into master. They fill device-tree firmware folders needed for audio and compute DSPs. github-actions[bot] subsequently reported successful publication to edge/aarch64, establishing package availability beyond the merge.

Further master-branch work by birkskyum added Windows Update firmware recipes for five Lenovo laptops in omacom/omarchy-pkgs@6fc27c436756. Quattro commits added the Flex 5G's missing device trees to the live image and selected the LCD IdeaPad Slim 5x's own tree to address brightness control, in omacom/omarchy-iso@fecb564ee7cb and omacom/omarchy@41c76fd4d69a.

Committed

Surface Laptop 7 fixes target unlock, audio and touch input

fidecastro committed Surface Laptop 7 15-inch board setup on quattro in omacom/omarchy@c421383753a1. It loads display, backlight and keyboard drivers early for disk unlocking and installs address and touchpad support, with a migration for existing installations.

Package-repository master commits by fidecastro address missing headphone output caused by an incorrect audio profile, retry touchpad service startup when the boot-time start is lost, and adjust touchpad clicking and touchscreen taps. These are committed changes in omacom/omarchy-pkgs@e0bb86e757a0, omacom/omarchy-pkgs@77b9bce4fbad and omacom/omarchy-pkgs@ea0214768605.

Open proposals

Hotspot review tightens saved credentials and retry behavior

ujo4eva's omacom/omarchy#7435 remains an open proposal for NetworkManager-backed hotspot controls, including band selection and QR sharing. During the coverage interval, greptile-apps[bot] identified that saving settings could make the panel and QR code advertise credentials that the active radio had not adopted.

ujo4eva reported changing active saves to restart the access point. A subsequent review found that canceling firewall authorization could leave saved and running credentials different, with an identical retry incorrectly reporting success. ujo4eva then reported adding a pending marker so a retry completes firewall setup and restarts the hotspot before clearing it. These are revisions to the proposal, not merged hotspot availability.

Open proposals

Omareader seeks a combined browser-theming implementation

Hank-dev's open omacom/omarchy#18736 proposes an optional browser extension that repaints pages using Omarchy colors and follows theme changes. As background, badenpiland offered on November 14 to combine it with a separate Omareader using Dark Reader's engine. On November 15, Hank-dev accepted that direction conditionally, inviting a contribution that would be tested before making this the combined proposal.

Review also produced concrete revisions: greptile-apps[bot] warned that the CSS size limit applied after the entire response was read and that theme tests silently skipped assertions. Hank-dev reported switching to bounded streaming reads and loading shipped palettes through the native host for those tests. The feature remains unmerged.

Open proposals

Desktop Restore revises agent hooks to require opt-in

The Desktop Restore verification request omacom/omarchy-plugin-marketplace#14221 remains open. HANCORE-linux blocked approval of an earlier target because setup automatically inserted persistent Claude and Codex command hooks without separate consent. The reviewer explicitly did not claim prompt-text recording, external transmission or a bypass of Codex's trust step.

dmitry-solomadin responded with version 0.6.5 and a new target commit, reporting explicit per-agent consent, remembered refusals, and controls to enable or disable hooks later. github-actions[bot] reported compatibility validation passing for that target, while stating that the marketplace snapshot remains unchanged until publication succeeds. The supplied record establishes a revised update awaiting verification, not a published marketplace update.