Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-5052GitHub issuePublicReceived

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

Reported by calabrone42 · filed Sep 12, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #10978 (R-774). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

4.0.3 ships native messaging host installers without Brave Origin (fixed by #10292 on quattro)revision 1 · captured 2026-10-04 12:10 UTC via poll

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).

View raw text
## 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).

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.