Merged

Root image installation reaches Quattro with disk and boot safeguards

emirb merged omacom/omarchy-iso#216 into the Quattro development branch. It deploys a prebuilt root image and adds machine-specific packages instead of installing roughly 940 packages individually. The proposal credits hegjon with the original root image design.

The landing included fixes for custom storage layouts and boot names. emirb reported moving the image's files into additional mounted subvolumes and rejecting layouts the installer cannot safely place. greptile-apps[bot] identified a mismatch between custom boot filenames and validation; emirb reported fixing both to use the same prefix in omacom/omarchy-iso#216:discussion_r4371954341.

dhh also merged omarchybot's disk cleanup proposal, omacom/omarchy-iso#327. Whole-disk installs now release old RAID and LVM storage stacks before partitioning and record bounded disk diagnostics on failure. In a separate hardware report, emirb described four successful free-space installs on one MSI desktop, with the existing installation's checked partitions and boot data unchanged. Those reported results cover that machine and test configuration, rather than a stable ISO release.

Open proposals

Local coding models proposed for the agents panel

dhh opened omacom/omarchy#16590 to add local coding models through the agents panel and command line. The first hardware-specific recipe targets NVIDIA N1X and GB10 machines with Qwen3.8 27B TensorFold and a 200k context. It would download pinned images and weights, run the server under rootless Podman and configure pi to use it.

The proposal remains open against Quattro. dhh reports a working add and restart flow on a 64 GB N1X laptop, but lists removal, model switching, fresh-machine setup and selection through the panel among the untested paths. Documentation and a dedicated icon are also still missing.

Merged

ARM power profiles gain a working daemon and migration recovery

ryanrhughes merged dhh's omacom/omarchy#14737 into Quattro, replacing the stock power profile daemon with Omarchy's build. The change targets ARM policies unsupported by the stock daemon, allowing balanced and power-saving profiles to take effect and performance mode to be selected on AC. The proposal reports lower N1X input latency; those figures are author measurements.

During review, ryanrhughes changed the migration to leave stopped or masked daemons alone, preventing a failed profile request from blocking later migrations. greptile-apps[bot] accepted the recovery explanation and withdrew its pending-completion finding. A subsequent commit by dhh, omacom/omarchy@0f014d1f81d2, lets migration finish when an SSH update lacks permission to switch profiles, leaving login initialization to apply the profile.

Merged

System updates keep one authorization through AUR and boot checks

dhh merged omarchybot's omacom/omarchy#16568 into Quattro. The initial sudo authorization now remains active through AUR builds and boot verification, avoiding additional password prompts near the end of an update. Authorization is revoked after the boot check and on exit.

The proposal explicitly accepts that AUR build code runs while the sudo timestamp remains live, changing the previous authorization boundary. A separate Quattro commit associated with sanjyay, omacom/omarchy@e5df29b64a05, also allows system updates to finish when mise tool downloads fail.

Merged

Saved screenshots gain Open and Edit notification actions

dhh merged omacom/omarchy#16505 into Quattro, replacing saved screenshots' timed floating previews with notifications containing a thumbnail, size and Open and Edit buttons. Screenshot and clipboard-image commands use Omasnap's notification option, with catalog strings supplied for translation.

The proposal required a supporting released Omasnap package before merging because version 1.22.0 rejects the new option. The supplied package history also records the 1.23.0 recipe update associated with dhh in omacom/omarchy-pkgs@dcb7b6dfeafa. The shell integration is a development-branch change.

Open proposals

Shell accessibility work splits into smaller proposals

calebl announced that the broad shell accessibility proposal would become a draft and remain open as a reference while smaller pieces proceed. In omacom/omarchy#13212:issuecomment-6397346768, calebl described a first part covering named, pressable bar buttons and named panels, with an acceptance check reading the accessibility tree. Panel controls, choices and documentation would follow.

The broader proposal exposes roles, names, states and actions to assistive technology and requires a Quickshell build containing its accessibility fix. As background from October 20, diogochaves reported plugin testing that found text fields named after example placeholders and named rows missing from the tree. calebl accepted those changes for incorporation. The work remains proposed, with no merge recorded in these sources.

Open proposals

Playback and controller games could inhibit shell idle actions

eesoymilk opened omacom/omarchy#16533 to restore the ScreenSaver D-Bus interface after the shell idle service replaced hypridle. A helper owned by the shell would let browsers and players inhibit screensaving and locking, release requests when callers disconnect, and preserve the user's separate stay-awake setting.

eesoymilk also reported Steam's overlay successfully holding an inhibit during The Witcher 3, relevant because controller input does not reset the compositor's idle timer. greptile-apps[bot] subsequently reported that a test gap covering owner-issued release had been addressed. The proposal remains open against Quattro.

Open proposals

Mesa packaging gains M3 Air evidence while delivery checks remain

The open draft omacom/omarchy-pkgs#1591 received hardware reports for revised Mesa and Vulkan packages. scottjones reported a fresh desktop login and graphics correctness checks on a J613 M3 MacBook Air without Mesa opt-in variables, using a retained custom kernel and stated firmware. The report also found that the legacy mesa-m3 opt-out hook forced software rendering despite the new system driver.

chriskearney confirmed that migration issue and described a separate capability-aware hook fix. Later in-day reporting described installed candidate packages passing reboot and pixel checks on J293, J313 and J516S, while explicitly withholding J615 and full conformance qualification.

The proposal body was updated on October 26 and is current context rather than the original October 25 wording. It now targets a newer integration pin, with fresh package validation and final login qualification pending. Earlier hardware results do not qualify those exact artifacts, and the recipe does not enable the disabled native M3 kernel backends.

Committed

Translation workflow fixes accompany broader localized setup

Quattro commits associated with dhh repair two translation delivery failures. omacom/omarchy@63ac02e5452b allows translation jobs to run when extraction is skipped, while omacom/omarchy@3372ceb223c4 merges validated translation sync proposals directly so later runs do not overwrite their unmerged translations.

Other commits translate first-run invitations, Git setup, weather and input-method notifications, plus About screen headings and date-related information. The ISO also hides gum's hardcoded English key hints because its prompts already explain the actions. These are committed development changes across the shell and installer repositories.

Committed

Hibernation resume uses persistent filesystem identifiers

A Quattro commit associated with emirb, omacom/omarchy@6573c3d4866e, changes unencrypted hibernation setup to identify the resume filesystem by UUID. Kernel device names can swap between boots on machines with multiple NVMe disks, causing a cold boot instead of restoring the saved session.

The change also migrates eligible existing configurations and records a pending rebuild before changing the resume setting. Failed, skipped or interrupted boot-image rebuilds can therefore be retried by the next migration run. Device-mapper names on encrypted installations retain their existing treatment.

Closed

Omarchy Sync reaches the marketplace for moving desktop setups

smolamSK's Omarchy Sync was published to the marketplace, with github-actions[bot] recording publication in omacom/omarchy-plugin-marketplace#12673:issuecomment-6403794115. It exports desktop configuration, extra packages, plugins and themes, then presents an import plan and backs up replaced files on the destination machine. Optional secrets use an encrypted export section.

HANCORE-linux accepted the privilege and package-management capabilities for explicitly confirmed imports of trusted configuration and software. The review emphasized that executable configuration from an untrusted sender is not made safe by the import process. The publication verification applies to the exact reviewed marketplace snapshot and is not a security audit.