Omarchy’s first-boot setup is getting the installer’s screens, plus OEM branding and an agreement step
Two pull requests merged on November 13 and 14, 2026 change the screens a new owner sees on a preinstalled Omarchy machine. Setup gets a language step and the installer’s look, and machine builders get a place for their name and terms.
Image: Omarchy (omarchy.org)
The next version of Omarchy will give machines prepared for someone else a much more polished first boot. That’s the setup run by omarchy-provision-owner, which finishes an install made for a future owner, and also runs after a factory reset. Two pull requests by @spencerbull, merged on November 13 and November 14, 2026, have it ask the installer’s questions on the installer’s screens, and then let an OEM put its own name on it. It’s a concrete piece of the factory preinstall picture from our earlier post, Secure Boot is coming to Omarchy, with factory preinstalls in mind.
The first change, PR #18783, starts from a simple observation: on the same machine, the installer and first-boot setup didn’t look alike or ask the same questions. First boot now uses the installer’s screens and order. It asks for the language, the keyboard, then the timezone, username, password and hostname, and ends on the same review table. Picking “No, change it” goes back to the keyboard step, as it does in the installer.
The language step is new. According to the PR, first boot used to have none, so both the form and the owner’s desktop stayed in English. The chosen language now becomes /etc/omarchy/language once its locale is generated, which turns it into the desktop’s language too. The setup also picks up the installer’s patched Terminus console font, its colours and its review table, and terminus-font joins Omarchy’s base packages.
The PR is upfront about a few limits. The new strings stay in English until the sync workflow translates them. On a 1920×1080 panel, the text is now smaller, because it matches the installer’s size. And a machine installed before terminus-font became a base package won’t have Terminus after a factory reset, so its first boot keeps the kernel’s font and stays in English, though the language picked still becomes the desktop’s.
The second change, PR #18841, is for OEMs building machines with the Omarchy ISO. Until now, first boot always opened on Omarchy’s logo and tagline, with no way to show a vendor’s name or have the owner accept its terms. The ISO can now place an OEM bundle in /etc/omarchy/oem, built with omarchy-iso-make --oem-config in the companion omarchy-iso PR #437, and first-boot setup reads it.
- Branding: the OEM’s text logo replaces Omarchy’s on the greeter and on the agreement screen, while the form steps in between keep Omarchy’s. The tagline and the logo colour come from
oem.json. - Agreement: if the bundle has an
eula.txt, accepting it is the last question, after the account review and before anything is created, so a machine whose owner declines is still as it left the factory. Declining offers to shut the machine down. - Record: accepting writes the OEM’s name, the SHA-256 of the text, the account and the time to
/var/lib/omarchy/oem/eula-accepted.json.
Because all of this runs on the Linux console before there’s a desktop, the PR spells out the constraints. The logo is text art, not an SVG or a bitmap, though it can be drawn in braille dots for four times the detail of block characters. An agreement in a script the console font lacks, such as CJK, Arabic or Hebrew, is refused when the ISO is built. Only those two screens are branded: the progress screen keeps Omarchy’s icon, and the boot splash and desktop are untouched.
The branding also survives a factory reset. According to PR #18841, the ISO lays /etc/omarchy/oem down before it takes the factory snapshot, which is what a reset restores, so the next owner gets the same branding and the same question, and the earlier owner’s acceptance record isn’t carried over.
