Capture an Omarchy install and replay it onto a fresh machine in one command.
Color type, which hid the shell's color palette and left the plugin's colors undefined. It now reads the palette as Commons.Color, the same fix Omarchy made for its own shell.Exec line is read as an argument list, so the three forms Omarchy has written parse: a bare URL, a bare URL followed by browser flags, and the quoted URL the current installer writes. A quoted launcher, and one carrying a Chromium profile flag, used to be captured and then refused on the machine that needed them — and the launchers Omarchy ships were captured in their place, so the category travelled the wrong set in both directions./usr/share/omarchy/applications is not captured: it is not this machine's state, and a fresh install has it already.omarchy-launch-or-focus-webapp form travel through the installer's custom-exec argument, assembled from validated pieces rather than copied out of the vault. A launcher whose second word is a command is refused.Exec line longer than a launcher could need (1024 bytes) is refused unread, so a fetched vault cannot buy a stall with one.ress verify, and left out of a shared loadout rather than published.ress status --json no longer exits 2 with no output when a setting holds a value it does not expect (INCLUDE_OMARCHY=, AUTO_INTERVAL_HOURS=24h), when the last-backup stamp is not a number, or when a vault's manifest is not JSON. The panel reads nothing but this command, so a blank panel was the visible symptom.file:// URL, a bare local