Merged

Local model installation stays inside the agents panel

dhh proposed and merged omacom/omarchy#18907 into the quattro development branch. First-model downloads and Add another Local AI now stay in the agents panel, showing package installation, download progress and failure reasons. Existing machines missing dependencies receive a graphical password prompt instead of a floating terminal.

greptile-apps[bot] identified a second model selection that could silently do nothing during package installation. dhh added a visible queue and clarified Delete behavior: waiting setups can be dropped, failures dismissed, and an active package installation left alone. The resulting commit, omacom/omarchy@0c6dc203863f, also includes Podman in fresh installs and the NVIDIA container toolkit alongside NVIDIA drivers.

Merged

OEM images install unattended and defer setup to the owner

spencerbull proposed and merged omacom/omarchy-iso#436 into quattro. Its OEM build installs encrypted across one eligible internal disk without asking questions, then reboots into owner setup. It refuses ambiguous disk choices, mounted storage and external media. The author reports OEM testing in x86_64 virtual machines; physical hardware and aarch64 OEM installs remain untested.

greptile-apps[bot] caught a release selector that could publish an unattended disk-erasing image under an ordinary ISO name. spencerbull confirmed the fix in omacom/omarchy-iso#436:discussion_r4571259461: releases now select date-named interactive images and stop if none exists.

Related commits on quattro add OEM branding, an agreement and factory setup scripts. omacom/omarchy@2c8d93be0bad asks for agreement acceptance before creating the owner's account and records acceptance. omacom/omarchy-iso@d6a2fdd6471b validates the bundle, runs OEM scripts before boot checks and the factory snapshot, and stops if those scripts alter the bundled agreement or branding.

Merged

Closing an update prompt releases the updater lock

ryanrhughes merged shbernal's omacom/omarchy#16045 into quattro. The fix keeps a plain Bash session leader above the updater so terminal loss ends the waiting prompt and releases its lock. A recorded process ID helps diagnose contention, while flock remains the authority for locking.

tobi reported an abandoned updater that had survived nearly seven days, then updated the contributor branch and its tests through maintainer edits. In omacom/omarchy#16045:pullrequestreview-5906052520, tobi reports that ordinary terminal closure passed on the unchanged base, while abruptly losing the script process stranded real gum; the patch passed both cases. This reproduces the observed process state without establishing why script originally disappeared.

Merged

Launcher entries gain app-specific dock behavior

dhh proposed and merged omacom/omarchy#18909 into quattro, adding Herdr, Agent and ChatGPT launcher entries with themed icons. Herdr receives its own application identity and focuses its existing window. Desktop entries can request a new window on a dock click or reuse a window on the current workspace. Existing installs receive the entries when their applications are refreshed.

greptile-apps[bot] found that the new policies could leave minimized windows inaccessible. dhh confirmed in omacom/omarchy#18909:discussion_r4574563670 that a click restores a minimized window before opening another. Separately, omacom/omarchy@f2fc529eba98 commits an Activity Monitor launcher for btop on new installs to quattro.

Merged

Dell XPS 13 and HP OmniBook receive audio fixes

ryanrhughes merged birkskyum's omacom/omarchy-pkgs#2657 into master, adding the Dell XPS 13 9345's speakers and microphones and correcting its four-channel speaker order. The proposal reports an owner's successful playback and microphone checks with the packaged build. github-actions[bot] subsequently reported kernel 7.3-61 and device trees 7.3-18 live on edge/aarch64.

costerou's omacom/omarchy-pkgs@49920caad8a3 adds the missing board-named audio topology for the HP OmniBook 3 14, whose sound card otherwise never registers. The companion omacom/omarchy@74de10479d3b commits installation and migration support to quattro. These are package master and runtime development changes, rather than evidence of a stable Omarchy release.

Merged

Snapdragon device trees expand to Kalambo and newer Surfaces

ryanrhughes merged birkskyum's omacom/omarchy-pkgs#2770 into master, adding Kalambo support, device trees for 15 Snapdragon machines and matching information for the Surface Pro 11 with 5G. The proposal says the new machines still need owner-provided hardware identification before automatic tree selection works.

greptile-apps[bot] identified missing kernel registrations for three proposed Surface trees. Those trees were deferred from the initial change. Subsequent master commits omacom/omarchy-pkgs@317ceb3168ae and omacom/omarchy-pkgs@8bd97d433662 add the kernel support and trees for the Surface Pro 12th Edition, Surface Laptop 13in 2nd Edition and Surface Pro 12in 2nd Edition. The Surface Pro 12th Edition's GPU remains disabled because this kernel cannot support it.

birkskyum also committed Kalambo tree inclusion to the ISO and runtime quattro branches through omacom/omarchy-iso@2b4d645ab8c6 and omacom/omarchy@2bab9efdff88, covering live-image staging, installed boot images and disk-unlock display setup.

Open proposals

Independent icon sets remain under review

dhh's open omacom/omarchy#18879 would separate launcher and dock icon shapes from themes while retaining theme-based colors. It offers Papercraft, pixel-art Arcade and Original app icons, plus custom sets installed from Git repositories. The packaging prerequisite is already committed on package master as omacom/omarchy-pkgs@88d516f3e3b7; the desktop proposal remains unmerged.

The proposal documents fixes following review for selection locking and replacement of custom sets, including preserving local work. greptile-apps[bot] subsequently raised a removal race in omacom/omarchy#18879:discussion_r4574695281 that could erase a newer icon choice. dhh also reports that live menu interaction and dock redraw have not yet been tested.

Open proposals

Scenes proposes reusable app and workspace arrangements

bronsontaylor opened omacom/omarchy#18858 to save named app arrangements and reopen fresh copies on empty workspaces. The open proposal captures supported browser tabs and profiles alongside layout and launch context. Private browsing sessions, unsaved documents and playback positions are outside its stated scope.

Review progressed through browser identification and restoration problems. greptile-apps[bot] flagged shared Chromium profiles blocking saves, then reported that the profile issue was addressed in omacom/omarchy#18858:issuecomment-6871273027. The author's final description reports native browser round trips and keyboard management actions, with live checks limited to one monitor. Scenes remains a proposal rather than an available merged feature.

Merged

Network warnings wait for a sustained Limited connection

dhh proposed and merged omacom/omarchy#18869 into quattro to suppress the brief red warning while NetworkManager probes a fresh connection. Limited connectivity must persist for three seconds before the warning appears; captive portals still appear immediately. A genuinely limited connection therefore takes three seconds to turn red.

greptile-apps[bot] identified a test gap around resetting the delay after a previous warning. dhh confirmed an added regression check in omacom/omarchy#18869:discussion_r4572402191. The proposal reports passing tests but no live network-switch trial.

Open proposals

Plugin update opt-in proposes individual holds

felipecpaiva's open omacom/omarchy#18868 would let users opt into plugin updates during an Omarchy update, before the shell restarts. It also proposes holding individual plugins out of bulk updates, useful for local modifications or a troublesome version. The toggle defaults to off, and explicitly updating a named plugin would bypass its hold.

greptile-apps[bot] found that the hold lookup uses directory names rather than manifest identities, allowing some held plugins to update. It also flagged directory-creation failures that could report a successful hold without saving one. These are review findings on the unmerged proposal.

Closed

Cooling is published after privileged helper fixes

ismoil77's Cooling submission, omacom/omarchy-plugin-marketplace#14955, reached publication, with github-actions[bot] reporting a published and verified marketplace snapshot. The plugin presents temperature and fan information, with an optional privileged Max action and automatic-reset service.

HANCORE-linux identified a privileged state-file problem in an earlier helper. ismoil77 responded with stricter directory ownership, file handling and fan-only restore data. HANCORE-linux accepted the reviewed capabilities and confirmed the finding fixed at the selected snapshot once helper 5 is installed. The reviewer explicitly cautioned in omacom/omarchy-plugin-marketplace#14955:issuecomment-6880648289 that updating the plugin alone retains an older installed helper. Marketplace verification applies to the snapshot and is not a security audit.