4.0.3 ships native messaging host installers without Brave Origin (fixed by #10292 on quattro)

[calabrone42]

Bug: Omarchy 4.0.3 ships Copy URL / Download Video native messaging hosts without Brave Origin support

Symptom

On the released omarchy 4.0.3-1 (installed via the omarchy repos, built 2026-09-08), installing Brave Origin as the browser does not wire up the bundled Chromium extensions' native messaging hosts:

• Copy URL (Alt+Shift+L) loads and its command fires, but nothing is copied to the clipboard.
• Download Video (Alt+Shift+D) loads but never hands the URL to yt-dlp.

Both extensions fail silently: they rely on chrome.runtime.sendNativeMessage('com.omarchy.copy_url' / 'com.omarchy.ytdlp'), and the host manifests are never registered for Brave Origin, so NativeMessagingHosts/ in the Brave Origin profile stays empty.

WhatsApp Slim is unaffected (it's a plain content script).

Root cause

omarchy-install-chromium-copy-url and omarchy-install-chromium-ytdlp enumerate the Chromium-family profile roots in their browser_dirs array and only list:

• BraveSoftware/Brave-Browser
• BraveSoftware/Brave-Browser-Beta
• BraveSoftware/Brave-Browser-Nightly

but not BraveSoftware/Brave-Origin(-Beta/‑Nightly). Brave Origin is a first-class browser in Omarchy (menu entries, installer, theming, migrations), but the native messaging host installers miss it.

Verified hosts for Brave Origin would end up at:

• ~/.config/BraveSoftware/Brave-Origin/NativeMessagingHosts/com.omarchy.copy_url.json
• ~/.config/BraveSoftware/Brave-Origin/NativeMessagingHosts/com.omarchy.ytdlp.json

Already fixed upstream, missing from the release

This is already fixed on quattro by PR #10292 (“Register the Chromium native messaging hosts for Brave Origin”, merged 2026-09-05) – the two installers on quattro now include Brave-Origin, Brave-Origin-Beta, and Brave-Origin-Nightly.

However, the v4.0.3 tag (2026-09-08) does not contain the fix – the tag was cut from an earlier state, so the released package still ships the broken installers. Users on stable therefore hit this exact bug while the fix sits unreleased on the dev branch.

Suggested action

Cut a patch release (4.0.4) that includes #10292, or backport the two-line array additions to a 4.0.3 maintenance branch so stable users get the fix via a regular update.

Workaround (for affected users)

Eithe manually copy the two manifests from a Chromium-family profile (e.g. Brave-Browser/NativeMessagingHosts/) into Brave-Origin/NativeMessagingHosts/, or add the three BraveSoftware/Brave-Origin* entries to the browser_dirs arrays in both installers and re-run them. A full browser restart is required (Chromium caches the extensions' service workers across launches).

[bjarneo]

Automated duplication check: this issue looks similar to #10978, which covers the same brave Origin native hosts missing. I keep that one open and close this one to keep the discussion in one place.

If you feel this is the wrong decision, please open the issue again with a note on the difference.