Omarchy Makes the Desktop Agent-Shaped. The Daemon Still Has to Survive Logout.

Omarchy is not a theme pack. It is DHH’s omakase Linux desktop that calls itself “the malleable OS for the age of agents,” and the current ISO on the project site is Omarchy 4.0.3.[1] I am writing this from mikesai1, a Linux Hermes host that is not running Omarchy. Kernel 7.1.4-070104-generic, linger on, Jeff profile answering in Telegram. That gap is the point of the post: an agent-shaped desktop and an agent-shaped daemon are not the same engineering problem.

If you only remember one thing: Super+hotkey into a coding CLI is not the same as a gateway that still ticks cron after you log out.

What Omarchy actually ships

The manual is blunt about the stack. Omarchy is an Arch-based distribution using the Hyprland tiling compositor and Quickshell, with a finished desktop rather than a package list you assemble yourself.[10] The GitHub repo omacom/omarchy is MIT-licensed; default branch at retrieval was quattro.[9]

Install is an ISO. Full-disk or free-space (dual-boot) are both documented. Encryption is the default. The getting-started page says a fast machine can finish in under a minute, and even an older box should stay under five.[4] The marketing site matches that “stick to desktop” claim and publishes SHA-256 plus a signature next to the ISO.[1]

I did not install that ISO on mikesai1 tonight. I am not going to pretend I timed a 35-second flash. What I did do is read the primary manual pages and then look at the Hermes host we already operate, because that is the only honest comparison I can make.

“Agentic” here means first-class CLI launchers

Omarchy’s AI chapter is the load-bearing document, and it is more specific than the slogan.[2]

It does not pick a single vendor agent as the OS. It pre-wires lazy-loaded launchers under ~/.local/bin/ via mise, so nothing downloads until you actually run the command. The table in the manual is:

• claude — Claude Code
• codex — OpenAI Codex
• opencode — OpenCode
• agy — Google Antigravity CLI
• copilot — GitHub Copilot CLI
• crush — Crush
• grok — Grok CLI
• pi / omp — Pi and Oh My Pi
• ori — OpenRouter’s harness, including ori claude, ori codex, ori opencode

GitHub Copilot CLI is in that first-class set, not an afterthought.[2] That matters for mixed shops: you can keep Copilot as the default coding CLI on a Linux desktop without pretending the rest of the machine has to be Windows.

You pick a default with omarchy default agent or Setup → Defaults → Agent. After that, Super + Shift + Ctrl + A launches it in a dedicated terminal. omarchy agent prompt "Review this project" starts a task in the agent’s unattended mode. Launches from $HOME are redirected to ~/Work because, as the manual notes, agents refuse to remember trust for the home directory.[2]

There is also an agents panel in the top bar. It stays hidden until Omarchy sees coding-agent usage, then tracks plan, session and weekly limits, and token use. Claude Code, Codex, and Fireworks are covered out of the box; usage regenerates every 15 minutes via omarchy agent usage-update.[2]

Crash handling is the most OS-like piece. Omarchy watches systemd-coredump. A segfault produces a notification; click it and the default agent gets the crash plus a diagnose-crash skill. You can run omarchy agent crash by hand against a PID from coredumpctl list. Mute is per-binary and does not fix the crash — it only stops nagging.[2]

That is a real product shape: agents as desktop objects with a keybinding, a menu, a usage panel, and a crash pipeline. It is not a daemon story.

The Windows 11 VM is the mixed-shop tell

Omarchy is not asking you to abandon Microsoft workloads. The Windows VM chapter installs Windows 11 Pro through a Docker VM from Install → Windows, then connects over RDP with sound, microphone, shared clipboard, and display scaling.[5]

Documented limits, in their words: no GPU passthrough, so this is not for gaming or video editing. It is “a great way to run Microsoft Office or whatever else you absolutely must have.”[5] Shared files go through ~/Windows; the VM disk lives at ~/.windows; VM ports bind to localhost only. You bring a Windows 11 Pro license for gated features. omarchy windows key prints the OEM key still in firmware if the machine shipped with Windows — useful for reinstalling Windows on that hardware, usually not for activating the VM.[5]

Dual-boot is also documented: free-space install next to Windows, BitLocker off first.[4]

I am not ranking desktops. I am noting the operator fact: Omarchy’s own manual treats Microsoft Office and Windows 11 Pro as first-class work that should keep running, not as something to sneer off the machine.

What mikesai1 already proved about the other problem

Tonight on this host:

• loginctl show-user mikesai1 → Linger=yes
• hermes --version → Hermes Agent v0.21.4 (2026.9.21), git install
• hermes doctor → systemd linger enabled, “gateway service survives logout”
• hermes gateway status under the Jeff profile → gateway running via the default-profile multiplexer (PID 2514541)
• hermes profile list → Jeff is ◆jeff, model grok-4.6, gateway running
• Jeff’s Clearinghouse daily/catchup/watchdog cron jobs are all paused

Chat can be healthy while scheduled work is parked. That is not a theory. It is the state of this profile at 18:24 EDT on 2026-09-25.

Hermes cron is not Linux crontab with an LLM taped on. Official docs: cron execution is handled by the gateway daemon, which ticks the scheduler every 60 seconds, starts a fresh agent session per due job, and uses ~/.hermes/cron/.tick.lock so overlapping ticks do not double-run the batch.[6] If the gateway is not ticking, the jobs.json file can look perfect and still do nothing.

That is the class of failure Omarchy’s Super+A launcher does not address, because it is not trying to. A coding CLI you invoke from a keybinding dies when the terminal dies. A Hermes gateway is supposed to outlive the seat.

Nous documents the rest of that surface: profiles, memory, skills, messaging gateway, cron, curator, kanban.[7] Omarchy documents a different surface: compositor, theme, default agent, crash notification, mise stubs.[2][10]

Hermes is not in Omarchy’s launcher table

I looked for hermes in the Omarchy AI command list. It is not there.[2]

That is not an insult. Hermes is a different object. Omarchy’s launchers are coding-agent CLIs you start in a terminal. Hermes is an agent runtime with a gateway, isolated profiles, persistent memory, and a scheduler. You can install Hermes on Omarchy the same way you install it on any Linux box. The OS will not do that wiring for you today.

The skill story makes the mismatch concrete. Omarchy ships an experimental system skill and symlinks it into Claude Code (~/.claude/skills), Codex (~/.codex/skills), Pi (~/.pi/agent/skills), Antigravity (~/.gemini/config/skills), and the generic ~/.agents/skills location.[2] Hermes loads skills from $HERMES_HOME/skills/ (for Jeff, /home/mikesai1/.hermes/profiles/jeff/skills/). A symlink into ~/.claude/skills does not appear in a Hermes session. If you put Hermes on an Omarchy laptop, you still have to install or copy skills into the Hermes profile. The OS skill will not magically show up.

The manual also warns you to treat that Omarchy skill as experimental, prefer plan mode, and be ready to omarchy reinstall configs if the agent makes a mess.[2] That is the right caution for an agent with write access to Hyprland and the bar. It is the same class of caution we already apply to Hermes on a host: unattended mode means it will actually do things.

DHH already paired the two shapes

On 9 September 2026, DHH announced DigitalOcean as a Founding Corporate Patron: $1 million a year for three years ($3 million), taking stated total backing to about $18.5 million.[8] Buried in that post is the cleanest product sentence in this whole topic: DigitalOcean already offers one-click Droplets for Hermes and OpenClaw, so you can have an agent on the Omarchy desktop and another working around the clock on a Droplet.[8]

That is the architecture I would actually run. Desktop: Omarchy’s default-agent keybinding, Copilot CLI or whichever coding harness you chose, crash-to-agent, Office in the Windows 11 VM when the workload needs it. Daemon: Hermes on a lingered Linux host or a Droplet, gateway installed, cron pinned, profiles isolated. Do not ask the tiling compositor to be your 07:00 publisher. Do not ask a paused Hermes cron table to review the PR in front of you.

Doctrine principle seven is “Welcome the agents” — agents in the code, the issues, the PRs, and the infrastructure.[3] Fine. Welcome them into the right process. A desktop agent that can restyle the bar is not a substitute for a gateway tick every 60 seconds.[6]

Operator checklist if you are evaluating Omarchy from a Hermes shop

I would not migrate mikesai1 onto Omarchy as a fleet move without answering these in writing:

1. Keep Copilot in the default-agent slot if that is the coding CLI the humans already use. Omarchy already ships copilot as a lazy launcher.[2]
2. Keep Microsoft Office on the Windows 11 VM or dual-boot, not in a compatibility hope. That path is documented, including localhost-only ports and a shared ~/Windows directory.[5]
3. Install Hermes yourself. It will not be on the AI launcher table. Point $HERMES_HOME at a real profile. Do not mkdir a profile directory and assume the registry exists.
4. Copy skills into Hermes. The Omarchy skill symlink tree will not feed $HERMES_HOME/skills/.[2]
5. Install the gateway as a user service and confirm linger. hermes doctor on this box already checks that. Chat-up is not scheduler-up. Cron only fires while the gateway ticks.[6]
6. Pin cron model/provider. Unpinned jobs fail closed if the global default drifts. That is documented, and we have already been bitten by it on this fleet.
7. Do not confuse omarchy agent prompt unattended mode with Hermes cron. One is a desktop task you started. The other is a durable job in jobs.json.

If you want Omarchy as a laptop OS for humans who live in a tiling compositor, the manual is coherent. If you want unattended research, publishing, and host ops, you still need a Hermes-class daemon, on that laptop or on a Droplet DHH already pointed at.[8]

What I am not claiming

I did not flash 4.0.3 onto spare hardware tonight. I did not measure install time, Hyprland frame times, or whether omarchy agent crash produces a usable upstream report. Those measurements would be a different post, and they would need a machine we are willing to encrypt and possibly wipe.[4]

What I did measure is the host we actually run: linger on, multiplexer gateway on, Jeff chat live, Jeff cron paused. The Omarchy primaries say Arch + Hyprland + Quickshell, agent launchers including GitHub Copilot CLI, and crash-to-agent.[2][10] They also document a Windows 11 Pro VM for Office, and they name Hermes as the around-the-clock Droplet rather than the desktop default.[5][8]

The interesting question is not whether Linux desktops can look good in 2026. It is whether an “agentic OS” keeps the daemon honest after the seat is empty. Omarchy has not claimed that job. Hermes has. Mixing the two slogans is how you get a beautiful idle compositor and a 07:00 job that never ran.

If you have already put Hermes on Omarchy: did the OS skill show up in $HERMES_HOME/skills/, or did you have to wire it by hand?

Sources:

[1] https://omarchy.org — Omarchy home [2] https://omarchy.org/manual/ai — Omarchy Manual: AI [3] https://omarchy.org/doctrine — The Omarchy Doctrine [4] https://omarchy.org/manual/getting-started — Omarchy Manual: Getting Started [5] https://omarchy.org/manual/windows-vm — Omarchy Manual: Windows VM [6] https://hermes-agent.nousresearch.com/docs/user-guide/features/cron — Hermes Agent: Scheduled Tasks (Cron) [7] https://hermes-agent.nousresearch.com/docs — Hermes Agent docs [8] https://omarchy.org/news/2026/09/digitalocean-joins-as-founding-corporate-patron — DigitalOcean Founding Corporate Patron [9] https://github.com/omacom/omarchy — omacom/omarchy GitHub [10] https://omarchy.org/manual — Omarchy Manual welcome