Jailbreaking Your Laptop · Part 1 of 5
Take Over the Machine
The lock moved from the carrier to the operating system. Sealed system volumes, notarization, telemetry you can't refuse. You own the silicon. You rent the software. This is the install that flips that.
The geohot story is in its own essay. The short version: in 2007 a teenager cracked the iPhone's firmware and took ownership of the hardware. Jailbreaking your laptop is the same move aimed at a different layer — the OS itself. You are cracking the assumption that the vendor's operating system is the only one allowed on the machine you bought.
You replace it with Omarchy — David Heinemeier Hansson's omakase Linux. Omakase means the chef picks the menu: you get a curated desktop out of the box instead of spending a thousand hours configuring one from scratch. It runs on Arch and Hyprland. As of Quattro (v4.0.0, August 14, 2026), the bar, launcher, lock screen, menus, and password prompts all run inside one program called Quickshell — instead of the old pile of background tools you could not name.
What leaves: update servers you never chose, identity checks that phone home, telemetry you cannot refuse, the sealed system that decides what runs before you do. What stays: a short list of things you picked. If you cannot name a process running on your machine, it should not be there.
What you need
The ingredients for Part 1 are short. Most of the work is in the install itself.
- A laptop. 16 GB of RAM works. No GPU required. A Mac, a PC, or a Linux box you already run.
- A USB stick. 4 GB or larger. The ISO is under 6 GB.
- A wired or 2.4 GHz keyboard. This is a documented requirement, not a preference. Bluetooth cannot type your encryption password at boot — the Bluetooth driver is not loaded that early. The same rule applies in your computer's firmware settings. Use a cable or a dongle.
- The Omarchy ISO. Download it from iso.omarchy.org. You'll flash it to the USB stick in step 1.
Numbers from the Quattro walkthrough and the official Getting Started page.
Install Omarchy
This is the main event. The steps below come from the official Getting Started page. Follow them in order. The OS install is the one part of this whole series you do by hand. No AI in the loop. You want to feel the lock crack yourself. AI comes in from Part 2 onward, once the machine is yours.
-
Download and flash the ISO
Pull the image from iso.omarchy.org. It is under 6 GB. Flash it to a USB stick with balenaEtcherwith balenaEtcherwith caligula. What you are making is a bootable installer stick, not a live USB you run forever. Once the install finishes, the stick comes out.
-
Turn off Secure Boot
On a Mac, there is no Secure Boot to disable — skip this step and go straight to booting the USB stick. Hold Option as you power on to get the boot menu.Reboot into your computer's firmware settings (usually F2, F12, or Del at startup). Find the Secure Boot setting and switch it off. If you also see a TPM setting, turn that off too.Reboot into your computer's firmware settings (usually F2 or Del at startup). Find the Secure Boot setting and switch it off, if it is present. Secure Boot is a Microsoft security scheme, designed for Windows and Microsoft-affiliated Linux distributions. Omarchy will not install while it is on. This is not a flaw in Omarchy — it is the point. You are telling the hardware to stop deferring to Microsoft's idea of what is allowed to boot.Secure Boot is a Microsoft security scheme. If your machine shipped with Windows, it is likely on and Omarchy will not install until it is off. If your machine came with Linux, it may already be off.
-
Boot off the USB stick
Plug the stick in, power on, and hold Option until the boot menu appears, and pick the USB stick from the boot menu (F12 or the key your manufacturer assigned), and pick the USB stick from the boot menu. You will land in the Omarchy installer. If it does not boot, you are still on Secure Boot or the stick was not flashed correctly. Check both before trying again.
-
Choose your install type
Two paths. Full-disk wipes the entire drive and installs Omarchy as the only OS. Free-space puts Omarchy into unallocated space on the drive — that is how you dual boot. If you are keeping Windows, turn off BitLocker first; Omarchy cannot install into encrypted Windows space.If you are keeping macOS, make sure you have a free partition ready in Disk Utility before you start.If you are keeping your current Linux install, make sure you have unallocated free space on the drive. The installation defaults to full encryption either way. If you are using an existing drive, back up first. Full-disk means what it says.
-
Answer the configuration questions
The installer asks a short list: hostname, username, password, timezone — the basics. Confirm the answers, select a drive, and watch the install. On a fast machine it can finish in about a minute. On older hardware, still under five. There is no package selection screen. Omarchy is omakase — the menu is fixed.
-
Reboot into your new desktop
Pull the stick when the installer tells you. You are now in a tiled desktop with no dock and no icons. The first toast on login opens the keybindings list if you click it. That is the on-ramp.
Super + Kfrom anywhere shows every desktop binding, searchable. Super is the Windows key on a PC, or Command on a Mac. Your thumb already knows it.
That is the install. Six steps. The lock is cracked. The rest of this chapter is the short tour of what you just installed.
The keys that matter
Super + K is the only binding you have to memorize. It shows every desktop mapping on one page, searchable. The rest you learn by living in it for a week. The table below is the starter set. The full reference, including the Tmux and Herdr chords, is on the official hotkeys page.
| Keys | What it does |
|---|---|
Super + K | Show every desktop keybinding |
Super + Space | Omarchy menu. Apps, setup, install, update. |
Super + Alt + Space | Apps only |
Super + Return | Terminal |
Super + Shift + Return | Browser |
Super + C / Super + V | Copy and paste, including inside the terminal |
Super + W or Super + Q | Close a window. In a tiling window manager, closing a window means the app exits. There is no dock to minimize to. |
That last row is the one that catches former Mac users. On macOS, the red dot closes the window and keeps the app running in the dock. Omarchy has no dock. Close a window and the app is gone. If you wanted it minimized, you wanted it open. This is how tiling window managers work — there is no separate dock to minimize into. It takes about a day to stop reaching for a dock that is not there.
How tiling works
Omarchy uses a tiling layout called dwindle. Open one window, it takes the whole screen. Open a second, they split. Open a third, the active half splits again. You do not drag windows around. You do not fish one out from under another. The layout handles where things go. The navigation page covers the full set of movement and swap keys.
Workspaces are how you keep things separate. Super + 1 through Super + 4 (and beyond) jump to a workspace. The switch happens with a keybinding. No animation, no carousel, noExpose-style preview. You hit the number, you are there. Super + Shift + 1 sends the current window to workspace 1. That is the whole model. Windows tile within a workspace, workspaces switch with a number.
This is the part that feels strange for the first day and obvious by the third. You stop managing windows. You start naming what you want on screen and where.
What you unlock
Omarchy gives you a curated desktop out of the box. The omakase defaults are good. But Omarchy runs on Hyprland, and Hyprland is one of the most customizable window managers ever built. Once you know the keys, you can make the desktop look like almost anything. Theming, animations, blur, shaders, custom menus, custom bars — every pixel is editable. This is what the community does with it.
Those are contest winners from the Hyprland Hall of Fame. Every desktop you see there started from the same base you just installed. The bar, the launcher, the animations, the colors — all of it is configuration you can read and change. On macOS or Windows, you pick from a handful of wallpapers and call it customization. On Omarchy, you pick from a gallery of full desktop environments, or you build your own. That is the difference between a lease and ownership.
Install and update software
Software comes from Arch's package manager and the Arch User Repository — a community-maintained collection of packages that covers almost anything you would want. You do not run the package manager by hand unless you want to. The Omarchy menu handles it. Super + Space opens the menu. Install, update, and setup all live there. The full list of what is available and how to reach it is on the other-packages page.
Updates go through one menu path: Update, then Omarchy. Not a command you type by hand, not a separate package tool, not a background process checking in. One menu item. Before every update, Omarchy takes a snapshot of your system automatically. You do not opt in. You do not remember to do it. It happens.
The updates page covers the details, including how to handle the rare case where a package needs manual attention after an update.
Snapshots and rollback
Snapshots are automatic before every update. You do not schedule them. You do not trigger them. Omarchy takes one, runs the update, and if the update is fine you never think about it again.
If the update breaks something, reboot. At the boot menu, you will see a list of your snapshots — pick the one from before the update, boot into it, and you are back. The system snapshots page has the details. The catch: snapshots restore the system only, not your personal files. Your home directory — your documents, photos, configs, everything under your user folder — is not covered. This is by design. The system is reversible. Your data is yours to back up.
The workflow is short. Update breaks something. Reboot. Pick the snapshot from the boot menu. You are back. Fix the problem, run the update again, move on.
The payoff
The machine is yours. No cloud middleman. No telemetry you cannot refuse. No sealed system deciding what runs before you do. You installed a curated, minimal set of services you chose. You can customize it. Your rules, your keys, your processes. Only the apps you asked for should be running. If you cannot name a process, it should not be there.
This is the foundation the rest of the series builds on. The OS is the lock you just replaced. From here, the apps you run, the AI you talk to, the domain you claim, and the things you publish all sit on a machine you can read end to end. None of that works on a leased OS. All of it works here.
That is part one. The lock is cracked. The machine is yours. Next, you give it a brain — local AI on localhost. Onward to Part 2.