Back to all resources
Omarchy v4.0.3 MIT · free Bootable ISO, Arch-based LIVE

Give your old laptop an agent-native desktop.

A stock Linux desktop treats an AI agent as one more app fighting for permissions it was never designed to grant. Omarchy is DHH's Arch-based distribution built the other way, with Claude, Hermes and OpenClaw already part of the base install. It ships as a bootable ISO. The full-disk path wipes the drive, so back up first or use the free-space option instead.

By Raj Singh · September 2026 · 40k stars · v4.0.3, security-reviewed · 5 min read

WHAT IT LOOKS LIKE

A theme, a top bar, and an AI menu with the Claude desktop app already listed under Install. Nothing here is a plugin bolted onto a normal desktop, it ships in the base image and gets its own security review each release.

A dark dashboard showing a leverage curve, standing in for an OS built around agent workflows
The AI menu, part of the base installAgileSingh
BEFORE YOU INSTALL IT

The full install wipes the drive. The default path is a full-disk install, and it erases the selected drive completely. Back up first, or use the free-space install to dual-boot instead of replacing what is already there.

Disable Secure Boot and TPM first. Both need turning off in BIOS before the installer will run. This is the step that silently blocks a first boot for most people who skip it.

Bluetooth keyboards fail at startup. Full-disk encryption means Bluetooth has not initialized yet at the point you need to type a password. A wired or 2.4GHz keyboard is required for setup.

It ships from a bootable ISO. Write it to a USB with balenaEtcher or caligula and boot from that, not a curl-to-shell script. There is no in-place upgrade path from an existing Linux install.

Licence, in plain English: MIT. Free for personal or commercial use, fine to fork and rebrand, no obligation beyond keeping the licence file.

Honest limitThis is a full OS commitment, not a package you can uninstall if it does not fit. The free-space dual-boot path is the only way to try it without giving up your current install.
Read the whole setup

Get the setup that works.

Drop your email and unlock the rest: what you need, the safe dual-boot install path, the BIOS settings to change first, and how to recover if the first boot fails.

One email. No follow-up unless I ship something that fits.

WHAT YOU NEED
  • A machine with Secure Boot and TPM disabled in BIOS
  • A wired or 2.4GHz keyboard, not Bluetooth, for the first boot
  • A USB stick, 8GB or larger, and balenaEtcher or caligula to write the ISO
  • A full backup, before choosing the full-disk install path specifically
INSTALL

Free space first, full disk once you are sure

The dual-boot path installs into free, unpartitioned space next to an existing OS. It is the reversible way to try Omarchy before committing a whole machine to it.

The prep

before booting the USBBIOS settings
1. Disable Secure Boot 2. Disable TPM 3. Shrink an existing partition to free unallocated space, if dual-booting 4. Boot from the USB and choose the free-space install option

Windows dual-boot needs BitLocker disabled first too, or the installer cannot see the free space correctly.

Prove itA successful first boot lands on the desktop with the top bar and AI menu visible. If it drops to a text prompt instead, Secure Boot or TPM is still enabled.
CONFIGURE

The AI menu is the reason to be here

Agent tools are listed under Install > AI in the base menu, not hunted down as third-party packages. The Claude desktop app was added directly to that menu in the most recent releases.

system menuwhat ships in the base image
Install > AI → Claude desktop app → Hermes integration → OpenClaw integration
SettingDefaultWhy I change it
ThemeT3 (current default)Cosmetic, but the manual has a dedicated guide for making your own if the defaults do not fit.
Security updatesmanual per-releasev4.0.1 through v4.0.3 were all security-fix releases. Update promptly rather than staying on an older point release.
Security teamOmarchy now has a named security team reviewing releases, per the changelog for v4.0.1 through v4.0.3. Report anything you find through the responsible-disclosure process at omarchy.org/security rather than a public issue.
DAILY DRIVING

It is still Arch underneath

Every Arch and Hyprland skill you already have still applies. The manual is the fast path for what Omarchy changed or added on top.

  • Read the manual first. It is the authoritative source, shipped in the manual/ folder and mirrored at learn.omacom.io.
  • Use the Omarchy CLI. A router command covers day-to-day tasks the manual documents under 14-omarchy-cli.md, rather than raw pacman calls for everything.
  • Check `omarchy-on` before assuming. Hardware-specific quirks, laptops, specific chipsets, are tracked there rather than scattered across issues.

Coming from Mac or Windows has its own manual page, worth reading before you start renaming muscle memory to Omarchy's keybindings.

WHEN IT DRIFTS

Two failures, both configuration

Installer will not boot
Secure Boot or TPM is still enabled. Both must be off in BIOS before the USB will boot into the installer at all.
Cannot log in at first boot
A Bluetooth keyboard has not initialized yet under full-disk encryption. Use a wired or 2.4GHz keyboard for the first login specifically.
RecoverySystem snapshots are documented in the manual under 47-system-snapshots.md, the intended way back from an update that breaks something.
THE SHAPE OF IT

Where everything lives

manual/the full documentation, authoritative over the mirror install/the installer scripts the ISO boots into config/default configs for the shell, apps and theming themes/the built-in themes, including the current T3 default agents/the Claude, Hermes and OpenClaw integration code

Dotfiles and further customization are documented in the manual rather than expected to be hand-rolled from a bare Arch install.

That is the whole setup

Free space first, full disk only once you are sure, and disable Secure Boot before any of it. What you get for the reboot is a desktop where the agent tooling was never an afterthought.

Open on GitHub →

↑ Unlocks the moment you submit the form above.

RS
WRITTEN BY

Raj Singh

I'm Raj Singh, founder of DebtOps.ai and a Claude certified partner. Over the last five years I've managed $25M in ads, built AI solutions for Fortune 100 companies, and installed AI operating systems and AI brains inside small businesses. Everything here is something I've shipped, debugged, or watched a client ship. My goal with AgileSingh is to make you irreplaceable in this AI age.

$25M
Ads managed · 5 yrs
F100
Enterprise AI builds
Claude
Certified partner
20
Guides shipped
More guides

Now wire an agent into the new desktop.

A desktop built for agents still needs the same operator manual and permission tiers as any other machine. The Claude Code setup guide is the config layer that goes on top.