App upgrades retain existing guest disks. The integration manager delivers reviewed guest features independently of the bundled factory image.
Open VM integrations > Review… in the Mac launcher. Launch Omarchy and paste
the supplied command into an Omarchy terminal. It mounts the app's dedicated
read-only 9p share at /mnt/try-omarchy-updates and opens a review. The share is
separate from the optional personal shared folder and needs no SSH connection.
Choose Install/update integration support and review replacements before confirming. Installation asks for the Linux user's sudo authorization, retains backups, and verifies each component before recording it as complete. Biometric enrollment remains a separate action. Existing PAM enrollment is preserved.
The guide is then available under Omarchy Menu > Setup > Try Omarchy
Integrations, or with try-omarchy-integrations in the guest terminal.
- sudo Touch ID: installs support; pairing is explicit and can be tested or repaired.
- Clock recovery: enables the RTC-based recovery timer and verifies it is active.
- Package compatibility: repairs both saved and active holds without upgrading packages.
- 1Password: optional per-user activation after installation, sign-in, system authentication enablement, and sudo Touch ID pairing. Service activation does not prove that a biometric authorization succeeded; test by locking 1Password without quitting it and using its unlock control.
The manager does not replace the kernel, upgrade the graphics stack, install 1Password, or reproduce every change in a newer factory image. Ordinary package updates remain with Omarchy Update. No VM reset is required for these integrations.
A dedicated virtio port carries bounded status reports to the host every ten seconds. Every VM launch starts a new check. After 120 seconds without a valid report the host shows that setup or repair may be needed and continues listening. An older, slow, or stopped guest agent cannot be distinguished by silence alone.
When setup, updates, or repairs may be needed, the app offers a review once per bundled integration revision for that disk. Choosing Later leaves the VM running and keeps the review action available. Checks still run on every launch.
The Mac menu bar provides a live integration status and review action. The launcher shows the last check for the selected persistent disk. A report of current components means installed files and relevant services passed inspection; it does not attest that Touch ID was successfully used. Status messages never execute commands or authorize host or guest installation.
The updater verifies the exact bundle inventory and hashes before installation, then stages a root-private copy. The app signature covers the bundle and manifest; hashes detect corruption and do not independently establish trust in an app.
Previous files, the previous installed bundle, and progress are retained under
/var/lib/try-omarchy/integrations. A component is marked complete only after
verification. Rerunning skips a previously completed step only when its files and
required services still match. This is resumable installation, not a transactional
rollback of all PAM or systemd effects. A failed step prints its error and leaves
progress and backups available for repair.
Installation lists existing integration files that differ before asking to replace them. Unrelated menu entries and package-configuration settings are preserved. Unsupported or unsafe paths stop the operation. Close Omarchy Update before installing integrations; the package-hold repair also uses pacman's lock.
Guest status diagnostics:
systemctl status try-omarchy-integrations.service --no-pager
sudo journalctl -u try-omarchy-integrations.service -b -n 40 --no-pager