Merged

Local models gain NVIDIA prerequisites and working launches without a default agent

dhh opened and merged omacom/omarchy#17330 into the quattro development branch, adding NVIDIA's container toolkit when local-model setup detects an NVIDIA GPU. The toolkit supplies the GPU device specification needed by model containers; N1x laptops previously lacked this prerequisite.

dhh also opened and merged omacom/omarchy#17337 into quattro. Local-model launches now select pi, or OpenCode when pi is unavailable, before checking for a default agent. This fixes a panel launch button that appeared inactive when no default was configured. The supplied testing covers the launcher path, while a live panel click remained untested.

Merged

Herdr Desktop joins Install > AI with Omarchy theme activation

ryanrhughes merged jankeesvw's omacom/omarchy#17132 into quattro, adding Herdr Desktop under Install > AI through Herdr's official installer. The app and its core update themselves. There is no Remove entry yet because removal needs a decision about preserving running terminals and user modifications.

The theme integration attributed to claytonfaria was committed to quattro in omacom/omarchy@4907fcdf74eb. During installer review, greptile-apps[bot] identified the missing theme dependency, and ryanrhughes said it would land first. After merging, ryanrhughes explained that installation waits up to 30 seconds for the app and activates its Omarchy theme, with a manual theme-picker fallback.

Committed

ARM graphics packages are realigned after dependency changes block upgrades

thepixelgardener-create reported blocked edge upgrades in omacom/omarchy#17368 after aquamarine and hyprgraphics changed their library versions. AmmonMatthews reported the same failure on Apple Silicon's rc channel and documented affected ARM packages. The issue remains open.

On the package repository's master branch, stevederico's omacom/omarchy-pkgs@edba40f9377e carries aquamarine 0.16.0 for aarch64. emirb's omacom/omarchy-pkgs@9f9775f75462 then rebuilds Hyprland as 0.57.0-4 against the new libraries and adds hyprgraphics as a rebuild trigger. These are committed packaging repairs; the supplied records do not establish successful upgrades across the affected channels.

Committed

Kernel packaging gains collision checks and a repaired publish step

emirb committed safeguards on the package repository's master branch after a real kernel and a transitional package produced the same package name. omacom/omarchy-pkgs@53f705bd6bb6 rejects duplicate package names and publication slots; omacom/omarchy-pkgs@326470ed1eca restores the kernel's own package base after a later version bump reintroduced the collision.

The extracted publication helper initially was not loaded in the publish step, preventing publication. emirb corrected that in omacom/omarchy-pkgs@6399d7ed3ea7 and added a workflow check for missing helper imports. omacom/omarchy-pkgs@934165435e86 also makes newly introduced namcap errors fail checks while reporting pre-existing errors separately.

Open proposals

Stable kernel fix is reported while the IPv4 backport proposal remains open

ChrisDrit's omacom/omarchy-pkgs#1785 remains open. The proposal, opened October 29, backports the IPv4 TCP use-after-free fix for CVE-2026-98432 to three kernel recipes; ChrisDrit disclosed that a full kernel build and boot test had not been performed.

In omacom/omarchy-pkgs#1785:issuecomment-6579785844, bogomind reported that stable listed linux-omarchy 7.2.15-1 on November 2 and that, after upgrading and rebooting one machine, inspection of its running kernel showed the corrected memory-release calls. bogomind therefore considered the proposal superseded. This is a contributor's reported verification, rather than a recorded closure of the PR.

Closed

Large-package download resets are traced to Cloudflare flow control

emirb closed GreyforgeLabs' omacom/omarchy#12049 after reporting that investigation traced intermittent package-download resets to an HTTP/2 flow-control bug in Cloudflare. emirb said users should no longer encounter the problem.

The original September 16 report described repeated failures fetching large packages over IPv6, with IPv4 downloads succeeding. The closure provides a reported infrastructure diagnosis and resolution; the supplied closing comment contains no fresh download measurements.

Open proposals

Snapdragon firmware proposal covers 33 machines as copied firmware gets retirement rules

birkskyum opened omacom/omarchy-pkgs#2037 to package OEM firmware for 33 Snapdragon X machines. The recipes unpack Windows driver archives without running their installers and verify firmware hashes. birkskyum reports building all 33 packages on aarch64; the proposal remains open.

greptile-apps[bot] initially found that remote table values could become executable shell text in generated recipes. Its later review summary says the command-injection finding was fixed through validation and quoting.

Separately, birkskyum's omacom/omarchy-pkgs@2a89ec9a8650 was committed to master. It retires unchanged firmware copies extracted from Windows once packaged firmware covers the device's complete set, keeping linked files together to avoid mixing releases.

Open proposals

Installer boot proposal reports faster startup alongside the themed menu

hegjon's omacom/omarchy-iso#355 remains open, proposing fewer boot reads, deferred startup work and a console logo that continues into the installer greeter. In a November 2 follow-up, hegjon tested a local rebase onto the themed-menu work rather than reporting a merge.

In omacom/omarchy-iso#355:issuecomment-6577701352, hegjon reports median QEMU USB 2 UEFI startup falling from 25.0 to 10.1 seconds and cold-start hardware measurements on a Samsung laptop falling from 37.2 to 17.1 seconds from firmware boot menu to greeter. These are the author's measurements. hegjon also identified a stale expected filename in the combined tests and reported that correcting it allowed the combined suite to pass.

Open proposals

Shell restart proposal handles stale compositor environments

dhh's open omacom/omarchy#16599 addresses updates that stop the shell but cannot restart it from a terminal missing the live Hyprland environment. The proposed launcher finds a running compositor and its display, and checks reachability before stopping the existing shell.

In omacom/omarchy#16599:issuecomment-6571808439, omarchybot reports reproducing a roughly 60-second failure on a disposable desktop and successful restarts in 0.4 to 1.0 seconds with the branch. omarchybot also pushed handling for inherited signatures pointing to a dead session. The proposal still awaits a maintainer decision; choosing between multiple live compositors remains a documented design question.

Merged

NVIDIA lock-focus repair gets testing on a second hardware family

As November 1 background, dhh opened and merged omacom/omarchy#17277 into quattro to restore password-field focus after NVIDIA's suspend-related VT switch and extend the first post-resume blank countdown.

On November 2, mudiam reported testing the patch on a ThinkPad P17 with a Quadro T1000 in omacom/omarchy#17277:issuecomment-6583434114. Password entry worked without clicking in three patched suspend cycles, compared with a failed unpatched attempt. mudiam did not test wrong passwords or early-blank timing and requested consideration for a subsequent 4.5 release candidate, noting the patch was absent from rc3.

Closed

Hyprdrive reaches marketplace publication after privacy and updater repairs

dragosol's Hyprdrive submission, omacom/omarchy-plugin-marketplace#11392, reached publication and closed. The listing supplies a settings panel for the native compositor plugin, whose overview, dock and experimental Mosaic layout still require users to build and install the native component against their Hyprland.

dragosol reported fixes that stop overview input during session locking, make debug logging private and remove user-owned legacy logs safely. HANCORE-linux's final static review confirmed all reported source findings fixed, including prompt handling and updater approval checks, without executing the plugin or tests.

github-actions[bot] recorded publication in omacom/omarchy-plugin-marketplace#11392:issuecomment-6581320002. Verification applies to the exact marketplace snapshot and does not constitute a security audit.

Closed

Hermes Face is published with private bridge access and an upgrade path

Xarrathh's Hermes Face submission, omacom/omarchy-plugin-marketplace#13625, was published and closed after revisions to its local bridge. The bar widget displays agent state and provides actions to focus the face, interrupt a turn and restart the service. A compatible Hermes agent CLI is a manual prerequisite.

Xarrathh reported fixes for peer identification, private file permissions, conversation text in process arguments and cross-origin requests. After HANCORE-linux found that healthy existing installations could keep running old server code, Xarrathh changed the update path to copy changed vendored files and restart the bridge while preserving configuration and history.

HANCORE-linux's final review accepted the documented service and package-management scope and identified the automated download-and-execute warning as a false positive. github-actions[bot] recorded publication in omacom/omarchy-plugin-marketplace#13625:issuecomment-6580895804. Optional speech uses Microsoft's Edge service, so spoken text leaves the machine.