Omarchy 4.6 brings monitor layout, resolution and refresh rate to the display panel
Arranging several screens on Omarchy no longer means editing monitors.lua by hand. DHH merged a redesigned display panel with a drag-and-drop layout map, per-display resolution and scale, refresh rates and rotation.
Image: omacom/omarchy #17159 (GitHub)
Multi-monitor setups are about to get a lot friendlier. “Monitor layout and resolution setting is coming for the display panel in Omarchy 4.6 (FINALLY!),” the official @omarchy account posted on X on October 31, 2026. The work landed the same day in pull request #17159, written and merged by DHH, followed within hours by four follow-ups adding refresh rates, rotation and cleanup.
The panel now shows one display at a time. According to the PR, the top of the panel names the display (“Built-in Display”, or else the monitor’s model), with a button per connected display to switch between them, and it opens on the focused one. Brightness, scale and resolution are now set per display. Text size stays a single global setting, since the shell font, GTK and the terminals each take one size.
Resolution options come from the modes each display actually advertises: its native size, then smaller modes of the same shape down to 1080p, capped at five. The PR gives two examples: a 6K Pro Display XDR shows 1440p, 4K, 5K and 6K, while a typical 4K monitor shows 1080p, 1440p and 4K. Behind the panel sits a new omarchy-hyprland-monitor-resolution command that refuses any mode the display doesn’t advertise.
Below that comes the layout map, which draws your active displays where they sit, at their relative sizes. Drag one against another’s side and it snaps to that display’s start, center or end. Keyboard fans get h and l to move the shown display left or right of the rest. A follow-up, #17170, adds a right-click menu on the map to rotate a display to normal, 90°, 180° or 270°, and makes the map appear even with a single monitor so a lone screen can be rotated too.
High-refresh screens are covered by #17175. When a display’s current resolution offers at least two rates of 60Hz or more and the fastest is above 60, a Refresh rate row appears under Resolution, with one pill per rate (for example 60, 120, 144). Near-duplicates like 59.95 and 60 collapse into one pill, and displays that only do 60Hz don’t show the row. The PR notes it has not yet been tried on a real high-refresh monitor.
Your choices are remembered by the physical monitor, not the port. They are saved in ~/.local/state/omarchy/monitors/settings, keyed by make, model and serial number. As the PR explains, a dock can rename connectors between plugs, so settings tied to DP-1 would land on whatever monitor showed up on that port.
Some things go away. The display list and turning displays on and off are gone from the panel, and Setup > Monitors leaves the Omarchy menu. monitors.lua stays for the extras the panel doesn’t cover, with commented examples for rotation, modes the panel doesn’t offer, keeping a monitor off, 10-bit color and VRR. Per #17166, a migration puts the new template on top of older monitors.lua files and keeps your own rules below it, saving the old file as a backup. That PR also reorders resize steps so a growing monitor no longer briefly overlaps its neighbour and triggers Hyprland’s layout warning.
If you’d rather keep full manual control, #17169 adds a switch: setting omarchy_monitor_panel_settings = false in hypr/monitors.lua leaves that file in charge of every monitor. The panel’s saved settings are then not applied, and any changes made in the panel last only until Hyprland reloads.
DHH is upfront about the rough edges. The PR lists known limits: moving a display makes the bar, background and dock close and reopen on each screen, which looks abrupt; pulling a display out of the middle of a row leaves a gap; and identical external monitors share one picker icon. A Codex review caught two bugs before merge, a resize that could push two neighbours onto each other and a stale brightness level, both fixed with tests.
All five PRs were merged into the quattro development branch. The official post places the feature in Omarchy 4.6; the post gives no release date.
