Desktop environments are usually an uninteresting topic for me, and I say that as someone who has been on Linux for about fifteen years, since graduate school ... a pretty good decision in my opinion. I default to Ubuntu because I want something that mostly just works and I never really cared about windowing or the desktop shell beyond "does the brightness key work."1 I took whatever the distro handed me and got on with the work.
That is the backdrop for why Omarchy surprised me. I've only run it in a VM so far, mostly browser and terminal work, so treat this as field notes rather than a daily-driver review. Omarchy is an opinionated Arch Linux distribution built around the Hyprland tiling window manager, where windows auto-arrange into tiles instead of floating free, and the marketing is not subtle. Omakase is Japanese for "I'll leave it up to you," which is mostly with respect to just taking what the Sushi chef decides what you should eat that day. Archy is because it is Arch underneath ... basically they are trying to say this is a chef's-choice Linux desktop, so don't patronize us if you're not interested. I find the pronunciation awkward and I would have just called it Omakase or Makase ... sounds better to my ear.
The metaphor mostly holds. It feels like sitting down at a high-end sushi counter where, for my terminal-heavy VM use while needing some browser stuff, eight out of ten courses are excellent and two of them are just not your thing. Below is my tasting menu from the VM.
Setup and the terminal
The speed of getting a usable linux machine is the part that is hardest for other distros to match with Omarchy. I am used to Ubuntu being "good enough" after install, then spending evenings chasing issues related to hardware and configuration quirks. Omarchy ships as if someone already did that pass for a scientist or researcher who lives in the shell. You could argue with the chef's defaults later on your own time, and those defaults will still fight you if your workflow is GUI-first or the guest hardware is weird, but the short answer is the time from install to a working nice configuration is extremely high.
If you love the terminal and TUI tools, meaning full-screen text apps rather than a bare shell prompt, which I really do, this is one of the most natural Linux desktop experiences I have used for that niche. The desktop does not treat the terminal as a leftover window you tolerate while hunting for a GUI.
 |
| Figure 1. Omarchy Hyprland desktop tiling layouts from the official manual |
Keybindings and tiling
The keybindings are different from what Ubuntu/GNOME, so a bit annoying for the ones already burned into my fingers. They are not hard to keep in your muscle memory once you accept that the chef rearranged the kitchen, but it still frustrates when I am mid-habit, and the main crux is that they are easy enough to learn by doing and slow to become automatic. That tradeoff is fine for what Omarchy brings to the table, and the more time I spend with it the more I suspect remapping my brain is worth it rather than a reason to bounce.
The tiling window manager is the course I keep chewing and not sure how I feel about it. Hyprland seems powerful and snappy, and information on screen is often presented better than on my usual Ubuntu desktop; think screen grabs, dictation etc. Still, the mental model is the hard part for me since I grew up floating windows and using overview gestures. Omarchy requires you to think in tiles and workspaces which I have never been confined to before. What I miss most is a native "show everything at once" key, basically what Super does in recent Ubuntu GNOME with the Activities overview. I want a panoramic dump of open windows when my brain loses the state of my desktop, not another "what's the right key binding for this?" hunt. I guess the tiling model is supposed to make that less necessary, since it automatically resizes windows, and the more I use it the more I think that is the real answer, I just have not put enough hours in yet.
 |
| Figure 2. GNOME Activities overview with open windows spread across the monitor, the Super-key habit from Ubuntu |
Little things and taste
The top-bar bits I noticed for dictate (voice-to-text) and set reminder feel natural and well manufactured, little things that usually take a plugin scavenger hunt on other linux desktops environments, and screenshots are similarly one of those chef defaults that just work without hunting. Screen recording has seemed broken or flaky in my VM, so I am chalking that up to the guest environment until I see otherwise. Worth saying so I do not oversell the polish.
The lack of a pinned app launcher bar is mildly annoying. Part of me still believes mousing over and clicking is as fast as typing the app name, at least for the three things I open constantly. You can keybind those, and the chef clearly expects you to. I am halfway convinced and halfway stubborn about it.
Some of the fonts and visuals are beautiful, some are just ehh, and the wallpapers, screensaver, and Omarchy logo are where I think the chef had a bad night. The screensaver in particular is one of those chef's choices that is just :nauseated_face: for me. Taste is personal, and this is the 2/10 dish in an otherwise strong meal.
Closing notes
Omarchy is a coherent, keyboard-heavy, terminal-native Arch/Hyprland stack with strong defaults and a few stubborn mismatches for someone coming from GNOME, and the more I live in the VM the more bullish I get on how well thought out the whole meal is. Things feel way way faster and more responsive in a VM than Ubuntu ever has. That could be the tiling model, the lighter shell, or just good configuration bias. I didn't measure any quantitative numbers so not going to pretend these are concrete facts.
The part I had barely touched in the tasting notes above, and the part that is shifting my stance, is how well AI coding agents seem to find their way around Omarchy compared with other distros I use. From poking at the docs it looks like both things are true, i.e. they ship an omarchy skill as breadcrumbs into the usual agent skill folders, and the omarchy CLI itself is self-documenting in a way that agents can actually navigate. Worth saying so I do not oversell it, the skill is labeled experimental and model quality still matters, but the feeling in practice is that agents just figure this desktop out faster. I am also a little sold on Herdr here, because it makes persistent sessions easy, and from there you can spin up teams and use the Herdr skill so agents actually talk to one another across panes. For my daily-driver agent setup I still prefer Agent of Empires, meaning my multi-agent fleet harness rather than a single CLI in a terminal, but as an OS layer for VMs where agents and terminals are the point, Omarchy is climbing toward the top of what I have tried.
My provisional stance is no longer ambivalent field notes with a slight nudge. I am probably not replacing Ubuntu on the metal yet, mostly because I have not put in the keybinding training hours, but for a VM aimed at browser plus terminal work Omarchy is near the top of the menu, eight excellent courses for that niche, two that are still not my thing, and a chef who is very sure about the meal.
Footnotes
-
To be honest, hardware quirks are a Linux stereotype with real history, but troubleshooting is much faster now. You can usually fix the problem in minutes with AI coding agents. ↩
