Sources
- Let the OpenClaw move finish when an OpenClaw of the user's own is in the way
- Move OpenClaw under a new migration that waits for its seed and finishes under omarchy update
- Revert migration-core changes from #14212
- Re-land OpenClaw as the seed after the release carrying omarchy#14212
- issue-comment by
github-actions[bot]
- issue-comment by
greptile-apps[bot]
spencerbull merged omacom/omarchy#14212 into quattro, retiring the old OpenClaw migration and introducing a new move to a self-updating user runtime. It fixes checks that failed under the update command's restricted PATH and adds gateway recovery.
spencerbull subsequently merged omacom/omarchy#15864, removing the general migration deferral mechanism: without seed files, the move now finishes without moving anything, with launcher recovery handling later setup.
emirb then proposed and merged omacom/omarchy#15875 into quattro. A conflicting user-owned OpenClaw command or gateway now leaves that installation untouched and allows the update to finish. Actual setup failures still leave the migration pending.
greptile-apps[bot] reviewed this distinction through code inspection and explicitly reported that it did not run tests.
Separately, spencerbull merged omacom/omarchy-pkgs#797 into master, restoring the seed package and removing OpenClaw from the fast ring.
github-actions[bot] reported version 2026.10.4-2 live on edge for both architectures in omacom/omarchy-pkgs#797:issuecomment-6252395093. That publication report establishes edge availability, not a stable release containing the quattro fixes.
