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.
Webapp crash takes down all browser windows — add process isolation option
Reported by lukeabbott · filed Feb 26, 2026Closed upstream on 2026-07-18. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
Problem
Webapps installed via omarchy-webapp-install launch with brave --app=URL, which connects to the existing main browser process. If a webapp crashes or the main process becomes unstable, all browser windows die simultaneously — including unrelated tabs and other webapps.
Crash report
- Brave: 145.1.87.190
- OS: Arch Linux, kernel 6.18.x, Hyprland/Wayland
- GPU: Intel Arc A750 (discrete), AMD Raphael/Radeon 680M (integrated)
- RAM: 32GB, 4GB zram swap
What happened:
1. Main Brave instance had been running ~4 days
2. Launched brave --app=https://grok.com at 08:33
3. Launched brave --app=https://outlook.office.com/mail/ at 08:36
4. At 08:36:29, the main Brave scope exited — all windows died
Resource usage at death:
- Main Brave scope: 13h 56min CPU, 6GB peak memory, 116MB swap
- No OOM kill in kernel logs, no segfault in dmesg, no crash dump generated
Proposed solution
Add an --isolate option to omarchy-launch-webapp that launches webapps with --user-data-dir=, creating a fully separate browser process tree. If the isolated webapp crashes, the main browser is unaffected.
This is browser-agnostic — --user-data-dir is supported by all Chromium-based browsers that omarchy-launch-webapp supports (Chrome, Brave, Edge, Opera, Vivaldi, Helium, and the Chromium fallback). The isolated data directory is stored under ~/.local/share/omarchy/webapps/<name> rather than any browser-specific config path.
Trade-off: Isolated webapps don't share cookies/sessions with the main browser, so users need to log in separately.
Usage
Interactive: omarchy-webapp-install prompts with a gum confirm asking whether to isolate.
Programmatic: omarchy-webapp-install --isolate "Grok" https://grok.com/ Grok.png
PR: #4749
View raw text
## Problem Webapps installed via `omarchy-webapp-install` launch with `brave --app=URL`, which connects to the existing main browser process. If a webapp crashes or the main process becomes unstable, **all browser windows die simultaneously** — including unrelated tabs and other webapps. ### Crash report - **Brave:** 145.1.87.190 - **OS:** Arch Linux, kernel 6.18.x, Hyprland/Wayland - **GPU:** Intel Arc A750 (discrete), AMD Raphael/Radeon 680M (integrated) - **RAM:** 32GB, 4GB zram swap **What happened:** 1. Main Brave instance had been running ~4 days 2. Launched `brave --app=https://grok.com` at 08:33 3. Launched `brave --app=https://outlook.office.com/mail/` at 08:36 4. At 08:36:29, the main Brave scope exited — all windows died **Resource usage at death:** - Main Brave scope: 13h 56min CPU, **6GB peak memory**, 116MB swap - No OOM kill in kernel logs, no segfault in dmesg, no crash dump generated ## Proposed solution Add an `--isolate` option to `omarchy-launch-webapp` that launches webapps with `--user-data-dir=`, creating a fully separate browser process tree. If the isolated webapp crashes, the main browser is unaffected. This is browser-agnostic — `--user-data-dir` is supported by all Chromium-based browsers that `omarchy-launch-webapp` supports (Chrome, Brave, Edge, Opera, Vivaldi, Helium, and the Chromium fallback). The isolated data directory is stored under `~/.local/share/omarchy/webapps/<name>` rather than any browser-specific config path. **Trade-off:** Isolated webapps don't share cookies/sessions with the main browser, so users need to log in separately. ### Usage **Interactive:** `omarchy-webapp-install` prompts with a `gum confirm` asking whether to isolate. **Programmatic:** `omarchy-webapp-install --isolate "Grok" https://grok.com/ Grok.png` **PR:** #4749
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.