Omarchy v4.5.0 compatibility checks and remaining gaps #45

This tracks the remaining menu-integration gaps and compatibility checks for Omarchy v4.5.0. The findings below were checked against Omarchy v4.5.0-rc2 and oma-cast 90efedd.

Applications already come from the installed app library, and Omarchy commands come from the current omarchy-menu.jsonc. Those lists update with the system. The gaps are mainly in how oma-cast handles the newer menu options.

Initial checks at 90efedd

• The Omarchy v4.5.0-rc2 menu parses successfully, including the new Appearance section.
• At 90efedd, 87 tests pass against Omarchy v4.5.0-rc2. One fails because it expects the old style menu ID instead of appearance.
• OmarchyMenu.js only has adapters for fonts and power-profiles. Omarchy v4.5.0 also uses languages and kernels, which aren't handled.

Remaining work

The kernel submenu, provider fallback and test updates were implemented in #46, merged on 28 October 2026. Language support remains separate in #32. Live desktop checks are partly confirmed below. Kernel switching has not been confirmed.

• Complete language selection and translated menu support in Omarchy menu never follows the system language, and the languages provider is missing (Language submenu shows "No results") #32. Keep the current-language indicator and allow searching by both the native and English language names. Not required for Omarchy v4.5.0 compatibility. The provider fallback from Adds kernel menus and provider fallbacks #46 opens language selection in the stock Omarchy menu. Native language support remains tracked separately in Omarchy menu never follows the system language, and the languages provider is missing (Language submenu shows "No results") #32.

• Add the Kernel submenu. Use omarchy-kernel list and omarchy-kernel get to show the available kernels and current selection, then build actions using omarchy-kernel set. Keep the menu's existing visibility check.

• Give unsupported menu providers a useful fallback. At the moment they're skipped, so a submenu can open with no results. Opening that submenu in the stock Omarchy menu would be a reasonable fallback.

• Update the test that expects style. Add separate Omarchy v4.0 and v4.5 menu fixtures, including checks that dynamic submenus get populated and unknown providers are handled.

• Check saved favourites, aliases and disabled-command settings against renamed menu IDs. Decision: accept the upgrade limitation and leave existing settings unchanged. No automatic ID migration is planned. See below.
  Live compatibility checks on Omarchy v4.5.0. The checked items were manually confirmed by Adam on 29 October 2026; no code changes were needed for those checks.

• App discovery after installing and removing an app, including launching it from oma-cast.

• Calculator operation and calculator history.

• Default-agent hand-off.

• Confirm calculator copy and paste specifically.

• Menu reloads.

• Provider refresh.

Kernel changes and other system actions should be checked separately from tests that only build the command.

Saved settings: accepted upgrade limitation

The existing oma-cast settings schema remains usable on Omarchy v4.5.0. Users can still save new favourites, and preferences for unchanged command IDs continue to apply.

Favourites, aliases and disabled-command settings are stored against exact command IDs. If Omarchy renames an entry, for example omarchy:style.font to omarchy:appearance.font, the old saved preference won't apply to the new entry. The saved data isn't deleted, but some favourites may disappear from the launcher after upgrading and need to be added again. Aliases and disabled settings for renamed entries may also need to be reapplied.

We're accepting this limitation. Preserving those preferences doesn't justify adding migration logic and risking regressions, including on Omarchy v4.0.0. We'll leave the existing data intact and let users recreate the affected preferences on v4.5.0. This completes the saved-settings check; it doesn't claim that the broader live desktop checks have been run.

The relevant files are plugin/services/OmarchyMenuSource.qml, plugin/core/OmarchyMenu.js and tests/omarchy-menu.test.js. Omarchy's installed shell/plugins/menu/Menu.qml has the language and kernel provider implementations to compare against.