Agents panel gains spending history and a local model download offer
dhh authored and merged omacom/omarchy#17560 into quattro, adding daily spending bars for the last 30 days without funding files. Fireworks and OpenRouter management keys supply account figures; other supported providers use estimated costs recorded locally by pi and opencode. Accounts with a monthly Fireworks cap retain a calendar-month meter and warning.
omarchybot reported follow-up fixes that preserve a known Fireworks cap when quota access is refused and keep previous spending visible as stale when billing checks fail. omacom/omarchy#17560:issuecomment-6750143617 explains that a key without quota access can still show daily costs when those remain readable.
A separate quattro commit, omacom/omarchy@0951985c4f1a, offers the catalog's recommended model directly on the agents panel when no local model is installed. Its Download action shows progress and speed, with keyboard access and cancellation. These are development-branch changes.
Shared tailnet models proposed for the agents panel
dhh opened omacom/omarchy#18296 to display and control models shared across a Tailscale network alongside local models. The open proposal adds sharing toggles, SSH pairing, remote start and stop actions, host memory figures and offline status.
The panel would refresh network discovery on opening and every 20 seconds while open. It depends on a companion engine branch; the proposal reports panel and translation tests passing, with live screenshots still pending.
Chrome default proposal exposes migration compatibility concerns
dhh opened omacom/omarchy#18240 to make Google Chrome the default for new installations, citing account sync and an author-reported performance comparison. The open proposal also packages signed copies of Omarchy's browser extensions and suppresses first-launch prompts. Existing installations would retain their browser.
greptile-apps[bot] identified two migration concerns: web apps could stop opening for existing Firefox or Zen users whose fallback is Chromium, and existing Chrome native messaging hosts would reject the new extension IDs. Its reviews requested a Chromium fallback and refreshed host registrations. Snapdragon video decoding in Google's ARM build also remains untested according to the proposal.
Snapdragon hardware support expands with an updated boot-tree fallback
ryanrhughes merged
birkskyum's omacom/omarchy-pkgs#2404 into master, adding device trees and firmware for the Dell Inspiron 14 5441 with X1P-42-100 and Lenovo ThinkCentre neo 50q QC. It also adds IDs selecting the LCD tree for Surface Pro 11 panels identified as LGD077b.
github-actions[bot] reported the kernel and firmware packages published to edge/aarch64.
The proposal explicitly says neither new machine's tree had been booted. Its author reported successful builds, while documenting incomplete hardware descriptions and an outstanding Dell speaker-profile requirement. The edge publication therefore does not establish working support across those machines.
dhh also merged
birkskyum's omacom/omarchy#17406 into quattro to embed an installed Snapdragon machine's own device tree. A later quattro commit, omacom/omarchy@c40eca98bdc3, restored the full tree list alongside that fallback: matching hardware IDs can select a newer tree after updates, while machines without a match retain their running tree.
ISO firmware staging proposal follows Snapdragon device-tree requirements
dhh opened omacom/omarchy-iso#419 to select live-medium Snapdragon DSP firmware from device-tree requirements instead of filename patterns. This would include firmware with different OEM naming and stage symlinked firmware as regular files that the boot hook can verify.
greptile-apps[bot] requested confinement of resolved symlinks to the extracted firmware tree and alignment with the live boot image's board selection. Its board-list finding explicitly says current Mahua boards do not suffer a boot failure from the mismatch.
The proposal remains open. github-actions[bot] reported an aarch64 install-test pass and an x86_64 failure in omacom/omarchy-iso#419:issuecomment-6753645227.
Bitwarden hibernation fix checks encryption across every swap path
dhh merged
birkskyum's omacom/omarchy#16212 into quattro. Bitwarden's secret-memory backend can disable hibernation while the application runs; the change selects its locked-memory backend only when every active disk swap passes the encryption check, preserving user overrides.
The committed implementation checks all backing paths, including volumes spanning encrypted and plaintext disks, rather than relying on encrypted root storage alone. As dated background, birkskyum's October 27 explanation in omacom/omarchy#16212:issuecomment-6453610392 states the tradeoff: hibernation becomes available, while Bitwarden gives up secret memory's protection against root reading its memory.
AUR failures would no longer suppress update boot checks
falkoro opened omacom/omarchy#18279 so an AUR package failure would record a warning while allowing the main update to finish boot verification, cleanup and the reboot prompt. This matters when a kernel upgrade has already completed before the AUR step fails.
emirb reported reproducing a real piper-tts-bin checksum failure in QEMU on stock 4.5.0-3: the existing updater stopped without a reboot prompt, while the proposed updater warned and finished.
emirb also requested stronger retry-warning coverage. The proposal remains open.
Package promotion safeguard adopts pacman's dependency resolver
birkskyum's open omacom/omarchy-pkgs#2354 would refuse promotions that introduce dependency failures and publish mutually dependent packages in one database update. That would prevent a kernel and its required companion package from reaching users in separate batches.
As November 8 background, emirb requested pacman's resolver after identifying a case the custom checker missed. On November 9,
birkskyum reported implementing before-and-after pacman checks for moved packages and their dependents, using the destination channel's Arch snapshot.
birkskyum subsequently asked how snapshot advancement should coordinate with promotion and whether emergency overrides should exist. The author reported refusals involving edge libraries and an x86_64 aurora-audio dependency mismatch; these are reported checker results, not independent verification.
Battery history proposal adds charge graphs and drain summaries
matijazezelj opened omacom/omarchy#18278 to show six-hour, 24-hour and three-day battery graphs, recent charging sessions and awake-versus-asleep drain. It reads UPower history through D-Bus and shares cached results across monitor panels.
After greptile-apps[bot] found that a cross-plugin import would break cloned battery services,
matijazezelj reported moving the history code inside the battery service and adding a clone regression check. Other reported revisions addressed keyboard navigation, right-to-left graph direction and sleep intervals.
The proposal remains open. The latest selected bot summary says the clone issue is fixed, while explicitly limiting its assessment to source inspection without running tests or the native interface.
Foamy Lock adds a layout editor while marketplace verification remains pending
foamrider advanced the update request in omacom/omarchy-plugin-marketplace#13968 with Lock Studio, a desktop lock-screen layout editor, 26 presets and additional modules and backgrounds. Later in-day updates moved the target to 1.3.3, reporting fixes for restoring drafts under Qt 6.12 and quitting cleanly when Studio's window closes.
foamrider reported validation and upstream main-branch merges.
github-actions[bot] confirmed compatibility at the requested target but required manual review for bundled executable binaries and remote source builds. The verification issue remains open, and its validation message says the marketplace snapshot stays unchanged until publication succeeds.
