Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
omarchy-launch-webapp: Opera ignores --app= so ChatGPT/Grok/X keybinds open the start page
Reported by Ojisan1 · filed Aug 25, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details
Dell XPS 14 DA14260, Intel Core Ultra X7 358H, Intel Arc B390 (xe), Omarchy 4.0.1-1, Hyprland 0.56.2. Default browser is Opera 135.0.5973.41-2 (opera.desktop) after removing Chromium.
What's wrong?
Stock webapp keybinds (Super+Shift+A ChatGPT, Super+Shift+Alt+A Grok, Super+Shift+X, YouTube, Calendar, etc.) and omarchy launch webapp <url> do not open the requested URL when Opera is the default browser. Opera starts (or the existing window is focused) on the start page / restored tabs instead of ChatGPT, Grok, X, etc.
Non-browser binds are fine (terminal agent, Spotify). Super+Shift+B also works, because it does not use --app=.
Steps to reproduce
- Install Opera, remove Chromium, set Opera as the default browser (
xdg-settings get default-web-browser→opera.desktop). - Press Super+Shift+A (ChatGPT) or run
omarchy launch webapp https://chatgpt.com. - Opera opens, but not as an app window and not on chatgpt.com.
Root cause
omarchy-launch-webapp treats opera* as a Chromium-family browser that supports --app=:
case $browser in
google-chrome* | brave* | microsoft-edge* | opera* | vivaldi* | helium*) ;;
*) browser="chromium.desktop" ;;
esac
exec setsid uwsm-app -- $(sed -n 's/^Exec=\([^ ]*\).*/\1/p' {~/.local,~/.nix-profile,/usr}/share/applications/$browser 2>/dev/null | head -1) --app="$1" "${@:2}"That produces opera --app=https://chatgpt.com. Opera is Chromium-based, but it does not honor --app=. The process is actually started with that flag (observed: /usr/lib/opera-stable/opera --app=https://grok.com) while the window still shows Opera's start page. Opera's own forums document the same behavior: --app= is ignored and you get a blank/new normal window.
This is distinct from #7034 (Firefox is not on the whitelist at all, so the helper falls through to a missing chromium.desktop). Opera is on the whitelist, so the launch "succeeds" and silently drops the URL.
Suggested fix
For Opera, pass the URL as a positional argument instead of --app=:
opera https://chatgpt.comThat opens a tab in the existing Opera window, or starts Opera with that tab if it is not running. --new-window also works but stacks extra windows.
A local workaround that rewrites --app=URL to a positional URL makes Super+Shift+A / Grok / X open the correct site as a tab. Happy to send a PR against omarchy-launch-webapp if that's useful.
Related: #7034, #5889 (Firefox path using --new-window because --app is Chromium-specific).
View raw text
### System details
Dell XPS 14 DA14260, Intel Core Ultra X7 358H, Intel Arc B390 (xe), Omarchy 4.0.1-1, Hyprland 0.56.2. Default browser is Opera 135.0.5973.41-2 (`opera.desktop`) after removing Chromium.
### What's wrong?
Stock webapp keybinds (Super+Shift+A ChatGPT, Super+Shift+Alt+A Grok, Super+Shift+X, YouTube, Calendar, etc.) and `omarchy launch webapp <url>` do not open the requested URL when Opera is the default browser. Opera starts (or the existing window is focused) on the start page / restored tabs instead of ChatGPT, Grok, X, etc.
Non-browser binds are fine (terminal agent, Spotify). Super+Shift+B also works, because it does not use `--app=`.
#### Steps to reproduce
1. Install Opera, remove Chromium, set Opera as the default browser (`xdg-settings get default-web-browser` → `opera.desktop`).
2. Press Super+Shift+A (ChatGPT) or run `omarchy launch webapp https://chatgpt.com`.
3. Opera opens, but not as an app window and not on chatgpt.com.
#### Root cause
`omarchy-launch-webapp` treats `opera*` as a Chromium-family browser that supports `--app=`:
```bash
case $browser in
google-chrome* | brave* | microsoft-edge* | opera* | vivaldi* | helium*) ;;
*) browser="chromium.desktop" ;;
esac
exec setsid uwsm-app -- $(sed -n 's/^Exec=\([^ ]*\).*/\1/p' {~/.local,~/.nix-profile,/usr}/share/applications/$browser 2>/dev/null | head -1) --app="$1" "${@:2}"
```
That produces `opera --app=https://chatgpt.com`. Opera is Chromium-based, but it does not honor `--app=`. The process is actually started with that flag (observed: `/usr/lib/opera-stable/opera --app=https://grok.com`) while the window still shows Opera's start page. Opera's own forums document the same behavior: `--app=` is ignored and you get a blank/new normal window.
This is distinct from #7034 (Firefox is not on the whitelist at all, so the helper falls through to a missing `chromium.desktop`). Opera *is* on the whitelist, so the launch "succeeds" and silently drops the URL.
#### Suggested fix
For Opera, pass the URL as a positional argument instead of `--app=`:
```bash
opera https://chatgpt.com
```
That opens a tab in the existing Opera window, or starts Opera with that tab if it is not running. `--new-window` also works but stacks extra windows.
A local workaround that rewrites `--app=URL` to a positional URL makes Super+Shift+A / Grok / X open the correct site as a tab. Happy to send a PR against `omarchy-launch-webapp` if that's useful.
Related: #7034, #5889 (Firefox path using `--new-window` because `--app` is Chromium-specific).
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.
- Out of scopeDecided by agents · verified · 2026-10-09 09:10 UTC