The next Omarchy turns on touchpad gestures by default
Three- and four-finger swipes now switch workspaces, open the Omarchy menu, summon the AI console and shuffle windows around, with an off switch for anyone who prefers their own.
Image: omacom/omarchy PR #16891 (GitHub)
Laptop users, get your fingers ready. DHH merged a pull request that adds default touchpad gestures into the quattro branch on October 28, 2026, and it’s coming in the next version. Until now, gestures in Omarchy were only commented-out examples in the config. Now a set of three- and four-finger swipes works out of the box.
It came fast. A day earlier, on October 27, 2026, DHH quoted Henrik Klee’s photos of his terminal “looking great in omaPad” and wrote: “Omarchy is a great fit for tablets, and we will make it better still. Tiling window managers are exactly what you need there. Add a few gestures for movement, and we will be flying.” The PR was opened and merged the next morning.
Here’s the full set, according to the PR description:
- 3 fingers left / right: previous / next workspace, empty ones included.
- 3 fingers up: toggle the AI console (
special:qconsole). - 3 fingers down: open the Omarchy menu, through the shell’s global shortcut so nothing new is spawned.
- 4 fingers left / right: move the active window to the previous / next workspace.
- 4 fingers down: toggle fullscreen.
One detail on the horizontal swipes: the workspace changes when the swipe ends, rather than using Hyprland’s tracked workspace gesture that drags the workspace under your fingers. DHH explains that workspace switching in Omarchy isn’t animated, and the dragging “felt off next to that.”
Want something different? Hyprland rejects a second gesture on the same fingers and direction, and the first one registered wins, so the defaults have to be cleared before you bind your own. You can unset a single one first with hl.gesture({ fingers = 3, direction = "up", action = "unset" }) and then bind its replacement, as shown in config/hypr/input.lua and the manual. Or turn them all off with omarchy_default_gestures = false in hyprland.lua, the same way omarchy_default_bindings works.
If you already set up your own gestures, you’re covered. A migration looks for an active hl.gesture( in ~/.config/hypr/*.lua, such as the horizontal-workspace example the manual used to suggest, and for those users only inserts omarchy_default_gestures = false above require("default.hypr.omarchy"). Their gestures keep working as before, with no config errors.
According to the PR, every gesture line was tried on a live Hyprland 0.56.2 session with no config errors, and the migration was run against several test setups, including a second pass over its own result. Swipe away!
