Omarchy for Developers: The Workflow DHH Built for Himself

Omarchy is the only mainstream desktop built by a working programmer for his own daily use, then given away. For developers, that shows up as defaults you’d have spent a weekend building: Neovim wired in, tmux on a hotkey, LazyDocker on another, and ten AI coding agents preconfigured before you’ve opened a config file.

You know the pitch by now — Omarchy is DHH’s opinionated Arch + Hyprland setup (our explainer), incubated at 37signals and now backed by the Omacom Foundation. This post is the developer-workflow tour: what’s actually wired up, and how to arrange it.

The dev stack on a hotkey

• Super + Return — terminal. Super + Alt + Return — a tmux terminal, sessions ready.
• Super + Shift + N — Neovim, preconfigured (LazyVim-style out of the box, not a bare init.lua).
• Super + Shift + D — LazyDocker, so containers get a dashboard instead of a dozen docker ps invocations.
• Super + Shift + Return — browser. Runtimes and language versions are managed with mise, which Omarchy uses throughout.

The window manager is the other half of the IDE. Hyprland tiles everything: editor and terminal split themselves, Super + J flips the split direction, Super + Alt + F goes full-width without leaving the tile layout. We wrote a whole training progression in Six Levels to a Mouseless Omarchy; consider it the prerequisite course.

The AI agent layer

The manual’s AI chapter says it plainly: coding agents are first-class citizens, but no favorite is picked for you. Ten CLIs ship as lazy launchers — claude (Claude Code), codex, opencode, agy (Antigravity), copilot, crush, grok, pi, omp, and ori — tiny mise stubs that download nothing until first run. Pick a default with omarchy default agent, and Super + Shift + Ctrl + A launches it from anywhere. In the terminal, a runs your default agent; cx is Claude Code and cy is Codex — and note the manual’s warning that those start in auto-approving modes.

Two touches you won’t find elsewhere: a top-bar agents panel appears once the machine sees AI usage, tracking plan limits for Claude Code, Codex, and Fireworks — and if something segfaults, Omarchy offers to hand the core dump to your default agent for diagnosis.

The room map for developers

Workspaces as rooms, jobs assigned:

• 1 — Code. Neovim + terminal split.
• 2 — Run. The app under test, browser dev tools.
• 3 — Agent. Claude Code or your pick, working a task. Check in with Super + 3, leave it alone otherwise.
• 4 — Infra. LazyDocker, logs, ssh sessions.
• 5 — Comms. Slack/email web apps, quarantined.

The agent room is the new pattern worth stealing: long-running agent sessions are background jobs with a face, and a numbered workspace beats a buried terminal tab. Kick a task off, exile the window silently with Super + Shift + Alt + 3, keep coding on 1.

Small quality-of-life stack that adds up over a day: Super + C / Super + V copy-paste that works the same in terminals and GUI apps, Super + Ctrl + V clipboard history, Super + Ctrl + PrintScreen OCR for grabbing error text from a screenshot someone pasted in Slack, and Super + Ctrl + S to beam a file to your phone via LocalSend.

The honest caveats

It’s Arch: rolling release, no LTS cadence, occasional breakage that expects you to read the news before updating — fine for people who read changelogs, wrong for people who want Debian-grade stasis. Secure Boot setups and corporate MDM stacks are friction. And the defaults are DHH’s taste; if you fight opinionated tools, you’ll fight this one. If you tend to trust good defaults, this is the fastest “format to first commit” experience on Linux right now.

This is part of our Omarchy productivity series. Also see Omarchy for streamers and Omarchy for writers. Install guides: Windows PCs, Intel Macs.