I looked at NixOS first because reproducible builds sounded like the right answer to config drift. the config language and rebuild model there is a much bigger jump if you're not already comfortable with a declarative approach, and I wanted something I could get productive on the same day. Omarchy still gets you a coherent, inspectable system, it just leans on plain files and Arch packages instead of a whole new configuration language
Flowtica Scribe
Hi everyone!
Omarchy is having a year. It is starting to look like the Linux desktop people will actually remember from 2026.
Linux has always exposed a lot of itself through files and commands. That used to mean more work for the user. With agents, the same thing suddenly makes the system unusually easy to inspect, change, and repair.
That makes omakase computing more interesting. @dhh can make strong choices up front without locking you into them. Agents make it much cheaper to disagree with him.
v4.0.0, aka Quattro is where Omarchy starts to feel less like a beautiful Arch setup and more like a desktop with its own point of view. The system is beginning to feel designed as one thing.
I still don’t think most of us really know what an “agent OS” looks like. But Omarchy is making the idea easier to see.
P.S. You can install @Steam right from the menu. How abt that?👊
Dial
"agents make it much cheaper to disagree with him" is a good line. the part I keep wondering about with an agent-editable OS is rollback - if an agent reshapes a chunk of your config while you're not watching and it's subtly wrong, is there a clean way to diff what changed and revert just that, or are you relying on dotfiles being in git and hoping you committed recently. feels like the same problem as letting an agent touch prod, just moved down to your desktop
Do people usually stick pretty close to the default setup, or does everyone end up turning Omarchy into their own thing