Chrome becomes the browser default as streaming web apps expand
dhh authored and merged omacom/omarchy#18240 into the quattro development branch, making Chrome the default browser for new installs while preserving existing browser choices. The change supplies signed versions of Omarchy's bundled extensions and enables Google account sync and Widevine streaming. The reported performance comparison is the author's measurement.
The Spotify change in omacom/omarchy@1a4cccd23eee ships a default web app across platforms while retaining native-client preference where installed. A follow-up attributed to Omarchybot, with omarchybot listed as a participant, namespaces its icon to avoid a package-file collision with native Spotify in omacom/omarchy@db31a2095e51.
Another commit attributed to Omarchybot adds Netflix. Its final recorded revision allows application refreshes and Restore Preinstalls to add the launcher to existing homes too, superseding earlier restrictions described in the same commit message. These are quattro commits, not evidence of a stable release. omacom/omarchy@551dc6296904
Sources
- Show and control the tailnet's shared models in the agents panel
- Open Qwen Code on local models, and count them and paired ones as local
- Show a model shared or unshared elsewhere on the tailnet within two seconds
- Pair and disconnect one tailnet model at a time
- Set up the SSH server before sharing a model
- Say how many machines use a shared model
The agents panel gains controls for shared tailnet models
dhh authored and merged omacom/omarchy#18296 into quattro, adding shared tailnet models beside local models in the agents panel. Users can pair over SSH, start and stop remote models, launch paired models and see when their hosts are offline.
Follow-up quattro commits reduce discovery polling from 20 seconds to two, make pairing and disconnection operate on individual models, and arrange SSH-server setup before sharing. Shared-model usage counts represent machines served within the preceding five minutes. omacom/omarchy@fcb41d664161 omacom/omarchy@ad7bd22a66ae omacom/omarchy@a37ca11dcf05 omacom/omarchy@f83473052679
dhh also merged omacom/omarchy#18515 into quattro to launch Qwen Code against local models and count paired-model usage as local. Qwen launching depends on a companion engine overlay; without it, the launcher falls back to pi. The proposal keeps the model key off command lines.
A top-level Agent menu unifies instructions and creation tools
dhh authored and merged omacom/omarchy#18363 into quattro. The new Agent menu exposes harness selection, shared instructions and Make something starters for themes, plugins and apps. Supported harnesses receive links to one shared AGENTS.md; differing existing instruction files are backed up with notification.
The app-creation tooling also moves from qmake6 to CMake through dhh's merged omacom/omarchy#18460, with CMake added for new and existing installations. Separately, a quattro migration correction limits rewriting to Omarchy's exact legacy dictation binding, preserving handwritten Lua bindings. omacom/omarchy@81c1843557a8
Files follow-ups repair migration losses and improve folder workflows
Background: dhh's replacement of Nautilus with the Folio-based Files merged into quattro on November 10 through omacom/omarchy#18378. November 11 commits repair a migration that could remove Papers and xdg-user-dirs, open terminals in the folder Files displays, and let previews fit smaller screens. omacom/omarchy@b6b6002d28fd omacom/omarchy@744e233cb6d5 omacom/omarchy@3543ebac50e1
The choice also prompted discussion. codeface-io questioned why Flea had not been used or developed collaboratively.
dhh responded that Files followed his personal aesthetics and pointed to keybinding customization for alternatives.
NjengaFelix proposed a file-manager selector under Setup Defaults; the supplied comment establishes a suggestion, not an implemented setting. omacom/omarchy#18378:issuecomment-6792570331 omacom/omarchy#18378:issuecomment-6792872863 omacom/omarchy#18378:issuecomment-6793221872
Signing-key changes remove public-keyserver dependencies from builds
emirb authored and merged omacom/omarchy-pkgs#2522 into master after reporting that the November 11 Canonical keyserver outage stalled builds and occupied builder capacity. Recipes now ship their trusted signing keys, and builds import those local copies. A daily refresh workflow checks for updates and revocations and reports changes for maintenance.
A related quattro commit, attributed to Emir Beganović with emirb listed as a participant, bundles the Arch Linux ARM bootstrap key and retrieves Omarchy's packaging key through its Web Key Directory with a pinned fingerprint. This addresses an update path that could stop when its keyserver fetch failed. omacom/omarchy@7c479641b1cc
Sources
- linux-omarchy-aarch64: add the LCD Surface Pro 11 (X Plus) (#2382)
- microsoft-surface-pro-11-support: support the LCD model and start the speakers at unity gain (#2379)
- Set up the LCD Surface Pro 11 (Snapdragon X Plus) on its own device tree (#18276)
- Add Surface Laptop 8 board setup (#16968)
- Set up the Surface Laptop 8 on existing installs (#18435)
- Acer Aspire 16 AI: speakers, headset and microphones (#2565)
- issue-comment by
birkskyum
- Acer Aspire 16 AI (A16-11M): wire lpass_vamacro for lid DMICs
Surface setup and Acer audio extend Snapdragon hardware support
Package-master commits attributed to Iván Ruiz, with rdereparadores listed as a participant, add LCD Surface Pro 11 kernel and device-tree support and extend its support services. They address backlight control, CPU frequency policies and speaker starting volume. A companion quattro commit selects the LCD model's own tree and migrates existing installations. omacom/omarchy-pkgs@52de3b11ff4e omacom/omarchy-pkgs@8cb43b328981 omacom/omarchy@b19ad9764d78
Surface Laptop 8 setup commits attributed to Jim Martin, with jdvmi00 listed as a participant, cover both sizes and existing installations in quattro. The setup loads drivers and firmware before disk unlock; USB4 router firmware extraction depends on Windows being present on disk. omacom/omarchy@ceb30ed19ab1 omacom/omarchy@e30e18c53ac8
For Acer Aspire 16 AI audio, a package-master commit attributed to Birk Skyum, with birkskyum listed as a participant, incorporates
GenericCPU's wiring, microphone clock and profile. In the still-open issue,
birkskyum announced edge-channel packages and requested testing with local overrides removed. That request leaves packaged hardware validation pending in the supplied discussion. omacom/omarchy-pkgs@ca8e47aadf38 omacom/omarchy#17555:issuecomment-6809158252
Plugin Guard 1.0.12 receives verified marketplace publication
mattwolfgang's request to publish a newer Plugin Guard snapshot completed with version 1.0.12 verified and available through standard installation.
HANCORE-linux confirmed successful approval, publication and deployment, and reported that the live catalog matched the reviewed commit. omacom/omarchy-plugin-marketplace#14622:issuecomment-6784747737
HANCORE-linux's preceding review accepted the exact snapshot after confirming fixes for bounded input, installer completeness, agent CLI isolation and HTTP worker ownership. The reviewer explicitly described remote source and artifact inspection rather than execution testing or a security warranty. Optional model review remains advisory, and Grok's user-configured lifecycle hooks remain a documented exception. omacom/omarchy-plugin-marketplace#14622:issuecomment-6784653919
Home-drive adoption remains open as reset safety receives review
dahankzter's open omacom/omarchy#18391 proposes adopting an existing home from another drive during setup and choosing whether to retain or erase it during factory reset. Its current description includes encrypted homes and homes inside another operating system's filesystem; this remains a proposal for quattro.
On November 11, greptile-apps[bot] identified a reset path that could erase the system disk.
dahankzter responded that checks in both reset staging and the erase worker addressed it and requested another review. A later bot comment raised a separate risk involving ordinary files beside a Btrfs home subvolume. These are timestamped review concerns; the supplied records do not establish that every concern remains unresolved in the current revision. omacom/omarchy#18391:discussion_r4536693269 omacom/omarchy#18391:issuecomment-6793431764 omacom/omarchy#18391:discussion_r4541153641
Installer proposal retries image verification before declaring corruption
GurpreetKang opened omacom/omarchy-iso#431 on November 11. The still-open proposal would re-read installation media after clearing caches when initial verification fails, distinguishing unstable reads from persistent corruption. Its current description, updated November 12, reports successful installation on the affected Dell and confines retries to the failure path.
In a November 11 response to review, GurpreetKang reported fixing an absolute-path error in mirror verification and adding timeouts to cold reads. The author reported passing new assertions while identifying remaining environment-dependent test failures. Those results are author-reported validation, and the proposal has not merged. omacom/omarchy-iso#431:issuecomment-6810102424
