Omarchy 4.5 cuts the menu’s slowest checks from 200 ms to 16 ms
DHH swapped three slow background checks for cheaper ones, and the hybrid GPU test no longer calls the tool that could wake a sleeping discrete GPU on every menu open.
Image: omacom/omarchy PR #15039 (GitHub)
Omarchy 4.5 makes three of the menu’s most expensive checks nearly free. “The Omarchy menu’s slowest checks went from 200 ms to 16 ms,” DHH wrote in the release notes published on November 4, 2026. The notes don’t tie that line to a specific change, but the numbers match “Make the menu’s slowest hardware and network guards cheap”, a pull request DHH opened on October 11, 2026 and merged into the quattro branch on October 12.
According to the PR, every menu open runs a batch of small checks, which it calls guards. On a Strix Halo desktop, three of them cost about 200 ms of a batch of roughly 410 ms: the hybrid GPU, touchpad and Wi-Fi QR Code guards.
The hybrid GPU check was the worst offender. omarchy-hw-hybrid-gpu went from 70-120 ms to 2 ms by counting PCI display controllers (class 0x03) from sysfs instead of calling lspci, which is what the omarchy-hw-nvidia* helpers already do. There’s a bonus here too. The PR points out that lspci reads PCI config space, which also resumes a runtime-suspended discrete GPU, and that was happening on every menu open. The supergfxctl path is unchanged.
The touchpad check dropped from 25 ms to 11 ms. On machines without a touchpad-named mouse, omarchy-hw-touchpad forked udevadm for every event device before checking whether Hyprland listed it as a mouse. Now it matches the name first and only asks udev about the candidates. “Same answers, same order,” the PR says.
The Wi-Fi QR Code row went from 65 ms to 3 ms. It used to run omarchy-network-status, with two nmcli calls and an iw call, just to find out whether the result started with wifi. A new hidden command, omarchy-network-wifi-connected, answers the same question with ip route, sysfs and two busctl calls.
Add up those three new timings and you get the 16 ms from the release notes. That doesn’t mean the menu opens in 16 ms. These are three checks measured on one machine, and the PR puts the whole guard batch there at 410 ms before and 256 ms after, as a median of five runs. The PR also says “the menu shows the previous run’s answers until it lands, so its runtime is how long a row can contradict the machine.” So the win is a shorter window in which a menu row can be out of date.
DHH checked that the cheaper versions still give the right answers. The PR says the hybrid GPU test now builds a sysfs PCI fixture and asserts that lspci never runs, and that on his machine the new hybrid GPU and Wi-Fi checks agreed with lspci and omarchy-network-status. The menu’s package snapshot, at about 75 ms, and its startup and icon work are handled in separate PRs.
