Kernel selection and desktop fixes reach Quattro as Surface support advances

01Choose the default boot kernel from the Update menu

dhh authored and merged omacom/omarchy#15966 into the Quattro development branch. With several kernels installed, Update now offers a Kernel menu that changes Limine's default after authentication, rebuilds the selected kernel and offers a reboot notification. The command refuses switches under Direct Boot and attempts to restore the previous boot configuration if switching fails.

The discussion settled a deliberate limitation: hand-edited boot orders beginning with a wildcard can leave the current-kernel checkmark unset. dhh explained that shipped settings and the selection command use exact kernel names; greptile-apps[bot] accepted that tradeoff and withdrew its finding in omacom/omarchy#15966:discussion_r4339204956.

02Monitor toggles and floating workspaces preserve personal layouts

dhh merged two fixes by zihaomu into the Quattro development branch. In omacom/omarchy#16147, re-enabling a display preserves the mode, position and scale of its existing named monitor rule. In omacom/omarchy#16143, personal floating-window rules registered after saved workspace modes take effect before the first matching window opens, preventing unwanted resizing and later tiling.

omarchybot reported reproducing both problems and checking the fixes on disposable Omarchy workers. Its display review also identified the boundary: customized wildcard and description-based monitor rules can still lose their layout. The floating-workspace change corrects ownership and exclusions; it does not establish a general fix for initial window-size negotiation.

03Surface Pro 11 packages land while board setup awaits a decision

turbineBMW's Surface Pro 11 board proposal remains open as omacom/omarchy#14390. Supporting commits reached the package repository's master branch, covering Wi-Fi, audio, camera routing, Flex Keyboard pairing, resume behavior, pen input and ambient light sensing. The package commits describe publication to edge; this is separate from acceptance of the board setup.

birkskyum's review required keeping the ARM-only packages out of x86_64 offline mirrors and completing an install using published packages. The mirror exclusion was committed on the ISO repository's Quattro branch as omacom/omarchy-iso@886f2899f1bb, and turbineBMW reported a successful fresh Surface installation in omacom/omarchy#14390:issuecomment-6323783042.

omarchybot subsequently said author-side prerequisites were complete but classification and the choice between competing support approaches still required a maintainer decision. The proposed setup targets the OLED model; LCD and X Plus variants remain outside its tested scope.

04Multi-user proposal tightens disk-key and account-removal safeguards

osbase77's open omacom/omarchy#16100 proposes local administrator and limited accounts, separate login identities, and changes to root access and automatic login when moving between one and several users. It would let people share a machine without giving every account administrator rights.

During the October 21 review, greptile-apps[bot] identified that a user-controlled recovery note could block account removal. osbase77 replaced that check with disk-key-slot checks before restoring automatic login. A subsequent concern about deleting a genuine recovery note led to a safeguard against deleting a home containing the standard-path note; osbase77 acknowledged that recovery after removing its owner can still require manual work.

CappieGold described Active Directory compatibility problems from an SSSD setup, including session unlocking and directory-group privileges. osbase77 kept this proposal scoped to local accounts and suggested building directory integration separately in omacom/omarchy#16100:issuecomment-6320386855.

05Native Podman proposal carries migration and recovery boundaries

acrogenesis opened omacom/omarchy#16173 to make Podman the native container engine, with optional Docker compatibility. The proposal puts development databases under rootless user services, preserves data during eligible Docker migrations, and moves the Windows launcher to authenticated rootful Podman while retaining its disk and credentials. It remains open.

greptile-apps[bot] questioned whether package queries detected alternate Docker providers. acrogenesis reported testing the actual pacman binary with isolated package databases and finding that those providers did resolve, classifying the finding as a false positive in omacom/omarchy#16173:discussion_r4337709418. The author also distinguishes current focused-suite results from earlier runtime evidence: a complete installation and engine migration were not repeated for this refreshed proposal.

06Captive-portal proposal pauses Tailscale exit nodes during sign-in

dhh opened omacom/omarchy#16186 to move connectivity detection to Omarchy's own endpoint and improve captive-portal sign-in. The proposed portal command temporarily pauses an active Tailscale exit node, watches for connectivity and restores it after sign-in. The network panel would also avoid showing misleading packet-loss measurements while internet access is unavailable.

greptile-apps[bot] flagged a locale-dependent completion check that could leave the exit node paused, plus notification strings that bypass translation catalogs. The proposal remains open. dhh's description also records cached browser HSTS as a known obstacle and says live exit-node pausing and a real captive-portal flow have not yet been tested.

07Installer safeguard would stop unreadable partition tables from endangering existing data

emirb opened omacom/omarchy-iso#307 after identifying a free-space installation path that could mistake an existing partition for a newly created one when the initial partition-table read failed. An existing Omarchy EFI partition could then be formatted or deleted during rollback.

The open proposal requires successful table reads before and after creation, with exactly one additional partition. If the result cannot be identified safely, installation stops rather than guessing. github-actions[bot] reported passing installation tests on both x86_64 and aarch64 in omacom/omarchy-iso#307:issuecomment-6322688377.

08Live ISO would boot the kernel a PC will actually install

emirb's open omacom/omarchy-iso#310 proposes booting linux-omarchy in the live environment on ordinary PCs while retaining linux-t2 for machines reporting Apple as their manufacturer. The aim is to exercise the installed kernel before installation, rather than encountering it for the first time behind the bootloader and disk-unlock prompt.

The proposal adds both kernels to the x86_64 image and estimates roughly three percent additional image size. github-actions[bot] reported passing x86_64 and aarch64 installation tests in omacom/omarchy-iso#310:issuecomment-6328144501; the proposal has not merged.

09Agent Voice publishes fixes for unsafe reads, Git hooks and private recordings

github-actions[bot] confirmed publication of a maintainer-reviewed Agent Voice update in omacom/omarchy-plugin-marketplace#12442:issuecomment-6327088335. The update also preserves leading minus signs in spoken prompts, correcting a reported case where a negative number became positive.

HANCORE-linux's review identified unbounded endpoint responses, execution of repository-configured Git filesystem-monitor hooks during permission checks, and permissive access to speaker models and older recordings. duaneoca reported reproducing and fixing these paths, including repairing existing private-data permissions at daemon startup. HANCORE-linux separately confirmed the bounded-response fix from source and later confirmed the Git fix before raising the permission issue.

The memory measurements and runtime reproductions are duaneoca's reports. Marketplace verification applies to the exact published snapshot and does not constitute a security audit.

10Omardeck combines overview, dock and notifications after review fixes

github-actions[bot] confirmed publication of QuokeCola's Omardeck in omacom/omarchy-plugin-marketplace#12449:issuecomment-6323100584. The plugin combines a window overview, dock and notification center. Its submission advises disabling overlapping overview, notification or dock plugins because they register the same gestures.

HANCORE-linux identified window titles being rendered as rich text, potentially causing shell-originated network requests. QuokeCola reported switching dock text to plain text and restricting title-related icon handling. HANCORE-linux subsequently accepted the optional touchpad-access rule and confirmed plain-text titles and private notification history at the reviewed revision. The core interface works without that optional gesture setup.

11Package tracking gains authenticated fetches and bounded retries

Package-maintenance commits associated with emirb reached master to address unreliable upstream tracking. omacom/omarchy-pkgs@4f04db9a0506 adds authenticated GitHub API requests and forces HTTP/1.1 for affected fetches. Its commit explanation attributes many recent failures to shared anonymous API limits and others to HTTP/2 errors.

omacom/omarchy-pkgs@b4c15a6898b2 adds bounded retries for transient failures and stages downloads before emitting their contents, avoiding concatenated partial responses after retries. A companion commit removes generic hourly branch-tracking failure messages from Basecamp while retaining failed Actions runs and package-specific logs.