Merged

Files replaces Nautilus across the desktop

dhh proposed and merged omacom/omarchy#18378 into the quattro development branch, replacing Nautilus with Files, packaged as folio. Folder defaults, dock pins and file-manager shortcuts move to Files, which includes column views, media previews, sharing and remote folders. The migration also removes Nautilus and Sushi from existing installations; the Nautilus transcode action has no Files equivalent yet.

The replacement exposed a provisioning dependency: Nautilus had brought in xdg-user-dirs, whose commands account setup still needs. birkskyum's follow-up, committed as omacom/omarchy@7a9a1e930921, explicitly installs that package for fresh installations and restores it through a migration on existing machines.

Merged

Plain becomes the editor default for new installations

dhh proposed and merged omacom/omarchy#18398 into quattro. New installations use Plain for config editing and text-file associations, while Neovim remains installed. Plain waits for its window when invoked as an inline editor and falls back to vi over SSH or in a terminal session without a display.

greptile-apps[bot] found that the migration could override editor associations saved in an older user MIME file. dhh changed it to honor both user locations before adding Neovim defaults, as recorded in omacom/omarchy#18398:discussion_r4530121703. Existing installations retain their editor choices, with Neovim preserved where no choice was recorded.

Merged

Qt applications adopt Omarchy colors through qtengine

outfoxxed proposed and merged omacom/omarchy#18325 into quattro, switching Qt applications from GTK-based theming to qtengine. The corresponding Qt5 and Qt6 packages were committed to the package repository in omacom/omarchy-pkgs@7d9ff3fa78f1. File pickers continue to use GTK through the desktop portal.

outfoxxed reported acceptable results across tested Qt applications and reduced memory cost per process. greptile-apps[bot]'s final source review reported that its earlier findings were addressed and described theme colors and icons following Omarchy settings; it performed no runtime or visual verification.

Merged

Gliff connections make every window capturable

dhh merged omacom/omarchy#18370 into quattro, allowing existing and newly opened windows to be captured while Gliff is connected. The override intentionally includes 1Password and Bitwarden and affects all screen captures during the connection. Original protection rules apply again after disconnect or service unload.

greptile-apps[bot] questioned the exposure of Bitwarden. dhh explicitly confirmed the broader scope in omacom/omarchy#18370:discussion_r4527144610. Review also prompted ownership tracking so cleanup from a retiring service cannot disable its replacement's active override, documented in omacom/omarchy#18370:discussion_r4527144960.

Merged

Local AI gains cabled Spark setup and model-aware starters

dhh proposed and merged omacom/omarchy#18338 into quattro. When another unconfigured DGX Spark is available over the ConnectX-7 cable, the agents panel offers setup at the top, with an option to hide it. greptile-apps[bot] found that reordering other providers could select the wrong action; dhh reported fixing reorder boundaries and cursor placement in omacom/omarchy#18338:discussion_r4527474477.

Related quattro commits make theme, plugin and app starters use a running local model, with Shift selecting the default agent instead, in omacom/omarchy@62ffc6b60359. dhh also added a Show logs action for local-model failures in omacom/omarchy@cfce7ad36b02, opening setup and model journals, including the other machine's log for a paired Spark model.

Open proposals

An open Agent menu proposal centralizes personal instructions

dhh opened omacom/omarchy#18363 to add a top-level Agent menu for harness selection, shared instructions and creation prompts. It remains open. The proposal links supported harnesses to one personal AGENTS.md file and shares creation commands between the menu and panel.

greptile-apps[bot] identified risks involving existing instruction symlinks, added Grok accounts and failed backup notifications. dhh reported changes that preserve or back up existing links, share instructions with Grok account homes and let editing continue when notifications fail. The final supplied review summary says those fixes remain in place; the proposal has not merged.

Open proposals

Chrome default proposal advances through compatibility fixes

omacom/omarchy#18240 remains open. dhh's proposal would make Google Chrome the default for new installations, suppress first-run prompts and install bundled extensions from locally shipped signed packages. Existing installations would keep their browser. The proposal's performance comparison is dhh's reported measurement, rather than independent verification.

In November 10 responses, dhh reported restoring Chromium as a web-app fallback, refreshing Chrome's native messaging hosts and moving browser flags into account seeding. greptile-apps[bot]'s final supplied summary considers the latest changes safe to merge. Snapdragon hardware video decoding in Google's arm64 build remains explicitly untested in the proposal.

Committed

Snapdragon device trees separate from kernel downloads

birkskyum's package change, committed on master as omacom/omarchy-pkgs@376292460383, moves Snapdragon device trees and hardware IDs into linux-omarchy-dtbs. Board changes can then ship without rebuilding and downloading the kernel for every Arm user. The package requires a kernel at least as new as the headers used to build its trees.

mrjbj's Surface Laptop 7 15-inch touchpad change uses that separation in omacom/omarchy-pkgs@89017e14297f, placing its board-only patch in the new package.

dhh merged omacom/omarchy-iso#419 into quattro so ISO firmware staging follows device-tree requirements instead of filename patterns. A follow-up rejects required firmware shipped as symlinks, avoiding copying files from outside an extracted package. birkskyum's omacom/omarchy-iso@4aebef1babbe lets staging read the new trees package too.

Committed

Snapdragon boot accessibility and ASUS hardware receive fixes

birkskyum's omacom/omarchy-iso@7fc74e66aa7b, committed on quattro, repairs the live screen reader's executable permissions and adds a Snapdragon boot entry that uses the live unified kernel image. Quiet boot keeps kernel messages from overwhelming speech. Snapdragon speech uses USB audio because the live image keeps the laptop audio DSP off.

Related quattro changes load the early display chain needed to show the encrypted-disk prompt on the ASUS Vivobook S 15 X Elite in omacom/omarchy@7dae86043e90, and install the board-specific audio package for ProArt PZ13 speakers and microphones in omacom/omarchy@e42e09f5d937. The Vivobook X Plus variant is explicitly left unchanged pending testing.

Committed

Release rehearsals build the packages a quattro release would ship

emirb committed twice-daily release rehearsals on the ISO repository's quattro branch in omacom/omarchy-iso@4c8e5cdd2035. They pin runtime and settings packages to quattro and run the install-test jobs against a rehearsal ISO, without publishing packages. This exercises release recipes that ordinary tests using lagging edge development packages do not cover.

The work also explicitly marks the ProArt PZ13 audio package as Arm-only and stops the build immediately if pinning fails. omacom/omarchy-iso@fd2b0b3aa815 keeps the published Neovim package in rehearsal images, matching the release path. These are development test changes, not a stable release.

Open proposals

Separate home-drive installation proposal faces data-safety findings

dahankzter opened omacom/omarchy-iso#424 to let installation adopt an existing home or prepare a fresh home on another drive. The proposed Home step appears when another disk offers a usable choice, with warnings about preservation and erasure. It remains open and depends on a companion runtime helper.

greptile-apps[bot] reported three substantial problems in the reviewed implementation: reusing an encrypted mapping for the wrong volume, validating home placement after root-disk erasure and silently creating an unencrypted home when a requested encryption key is missed. These are review findings on the proposal; the supplied records contain no subsequent fix response.

Closed

Foamy Media 1.3.3 publishes after binary and runtime review

Foamy Media's update request, omacom/omarchy-plugin-marketplace#14501, closed after publication of version 1.3.3. foamrider supplied public rebuilds and signed provenance for bundled cover-art helpers, then addressed tooltip markup handling, process completion, bounded diagnostics and dependency notices.

HANCORE-linux independently checked binary provenance, raised the tooltip and lifecycle prerequisites, and later approved the exact 1.3.3 snapshot after reviewing the fixes. The reviewer explicitly did not execute submitted code or tests locally. Publication and installation availability were independently confirmed in omacom/omarchy-plugin-marketplace#14501:issuecomment-6770083512.