Development source for the Apple Silicon macOS installer, extracted from maralcbr/omarchy-mx-mac into omacom/omarchy-mac-installer.
This first extraction preserves the installer behavior and Git attribution. The app is named Omarchy Installer and uses Omarchy's org.omarchy.installer identifiers (Packaging/identity.conf); the package removes a copy left under the old name, Omarchy MX Mac Installer, only when it already carries these identifiers. Integration with the shared Omarchy packages and Linux installation image is the next, separate change. This candidate is not an installation release.
Earlier preview and lab builds used com.omarchy.mx.installer. The new app has the same name, so it replaces the old one in /Applications, but it installs its own helper and never touches the old helper, state or a copy still named Omarchy MX Mac Installer: the old helper stays registered (and listed under Login Items in System Settings), and an install or removal record the old app left is not seen by the new one. Finish or clean up any interrupted install or removal with the old app before switching. To remove what the old app left:
sudo launchctl bootout system/com.omarchy.mx.installer.helper
sudo rm -f /Library/LaunchDaemons/com.omarchy.mx.installer.helper.plist /Library/PrivilegedHelperTools/com.omarchy.mx.installer.helper
sudo rm -rf /var/db/com.omarchy.mx.installer /var/db/com.omarchy.mx.installer.aside
sudo rm -rf "/Applications/Omarchy MX Mac Installer.app"
rm -rf ~/Library/Application\ Support/com.omarchy.mx.installer* ~/Library/Caches/com.omarchy.mx.installer
defaults delete com.omarchy.mx.installer 2>/dev/nullThe Application Support line also frees any image the old app downloaded. A Mac that ran the old installer package can also drop its receipt with sudo pkgutil --forget com.omarchy.mx.installer.pkg.
| Directory | Responsibility |
|---|---|
Sources/, Tests/, Package.swift |
Swift macOS app, trust core, helper, simulation and tests |
Engine/ |
Pinned Asahi source lock, Python overlay, build tooling and tests |
Packaging/ |
App and macOS package assembly |
Recovery/ |
Omarchy Step 2 GUI preview, standalone macOS 13 target and app packaging |
Release/ |
Inherited public trust root and release descriptor |
scripts/ |
Catalog and release tools, with fixture tests |
test/ |
Portable aggregate runner and extracted packaging tests |
evidence/ |
Recorded journal fixture required by the Swift tests and preview |
Firmware preparation needs HTTPS access to Apple's restore-image CDN (updates.cdn-apple.com) and, for AEA-encrypted inputs, Apple's public release-key service (wkms-public.apple.com or fcs-keys-pub-prod.cdn-apple.com). An offline Linux image bundle does not remove that Apple-input dependency. The helper requests only the admitted FCS key URL from the archive metadata; it sends no installation credentials. Range extraction checks the recipe, response extent, ciphertext authentication and resulting file hashes before publishing any firmware.
The helper is built from the Swift source in this repository, ported from Eryk Wieliczko's MIT implementation. Its recorded source hashes, toolchain, two-build comparison and binary digest are checked alongside the engine source lock. It ships in the app at Contents/Helpers/omarchy-restore-image, signed by the app's release signing (Developer ID, hardened runtime, secure timestamp, no entitlements), not inside the engine archive. The privileged helper passes an install's engine a root-only copy whose signature satisfies the app team's requirement, and the engine refuses to run an install without one. The helper requires macOS 14 or newer; the installer app already requires macOS 15 or newer.
Every catalog that offers a Mac release enables every supported Mac from one image: the 35 boards in scripts/supported-models.json, every M1, M2 and M3 Mac and the MacBook Neo (apple,j700). make-unsigned-catalog.py refuses inputs that miss, add or refuse one, and publish-channels envelope refuses to wrap a catalog that lists a Mac but leaves any of them out or disabled; only an empty "No Mac release yet" catalog lists none. The MacBook Neo and the M3 Macs are marked untested; the testing team qualifies them on real hardware on edge. os-promote does not re-check an envelope staged before this rule, so a rollback to an older catalog stays possible. The file also names the boards that stay refused and why: the M3 Ultra Mac Studio (apple,j575d), which the pinned v0.9.2 engine cannot inspect, and M4 and later (apple,j614s). M3 Macs run with software rendering (llvmpipe) until their GPU driver lands.
The portable suite requires Bash 5+, Python 3.12+, Git and standard Unix tools, including GNU sha256sum. It runs on Linux and can run on macOS with those tools installed:
bash test/allOn macOS, use a Bash 5 installation explicitly if the system Bash is older. The suite uses temporary fixtures and mocked publishing/SSH commands; it does not install anything. The source directory is sufficient; no desktop checkout or engine binary is needed for these tests. The Linux suite passed, followed by strict Swift formatting, 402 debug tests, 396 release tests and ad-hoc app assembly on an M4 Pro. The debug simulation also launched successfully; see the recorded validation and limits.
The Swift package requires macOS 15+ and Swift 6.2+. Follow validation.md for Xcode checks and a simulation-only review. App packaging additionally requires an authenticated engine archive; see the extraction prerequisites before following the inherited packaging guide.
Start by reviewing the standalone adaptations against the unchanged extraction. The original commit mapping and validation evidence are linked below.
Changes to main go through pull requests with approval from someone other than the author. The CI checks cover portable tests, Swift formatting and both Swift build configurations. Define the Linux image and shared package inputs in separate changes. Physical installation qualification follows the assembled image/package integration.
- Extraction provenance and boundaries: original revision, preserved history, inherited build issues and future shared-package integration.
- Validation and macOS handoff: what has been checked and what remains.
- Simulation guide: debug-only UI scenarios that avoid real installation.
The preserved release and cutover tools target the original publisher's infrastructure. They are not a release procedure for Omacom. Publishing, signing, privileged helper registration and physical installation require separate preparation and authorization.
The original MIT license, copyright notice and Git attribution are retained. External engine dependencies retain their own licenses; their exact revisions are recorded in Engine/source-lock.json.
The Apple Silicon image producer is image-builder/: mx-mac's build-mac-image, building from a signed candidate set with the authenticated candidate importer, and inspecting each image before it is packaged. See checks and entrypoints, how to build and one image producer.