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.
Menu briefly shows options that don't match the current state
Reported by felixzsh · filed Aug 6, 2026Closed upstream on 2026-08-07 by the merge of PR #6601 (closed by dhh). GitHub close reason: completed.
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
System details
omarchy quattro
What's wrong?
cases where i found this:
- Setup → Defaults → Browser: briefly lists browsers that aren't installed before settling on the installed ones.
- Trigger → Capture → Screenrecord: after stopping a recording, reopening the menu still shows "Stop Screenrecording" for a moment before it disappears.
-
The menu evaluates each row's visibility/checked condition in a single background step when it opens. With ~175 conditions, many shelling out to slow commands (package presence, default browser, hardware checks) the evaluation takes a couple of seconds, and until it finishes the menu shows the previous (stale) results.
I attempted a fix in #6594, but after testing I realized it isn't that simple the root cause is how visibility guards are evaluated.
Simply hiding rows until they're evaluated would make the menu slow to open. The proper fix i think is to make the evaluation fast caching/batching the expensive lookups. This probably affects many guarded rows beyond the two examples.
https://github.com/user-attachments/assets/22df0266-c0af-4ee9-9166-392c25b04943
View raw text
### System details omarchy quattro ### What's wrong? cases where i found this: - Setup → Defaults → Browser: briefly lists browsers that aren't installed before settling on the installed ones. - Trigger → Capture → Screenrecord: after stopping a recording, reopening the menu still shows "Stop Screenrecording" for a moment before it disappears. - The menu evaluates each row's visibility/checked condition in a single background step when it opens. With ~175 conditions, many shelling out to slow commands (package presence, default browser, hardware checks) the evaluation takes a couple of seconds, and until it finishes the menu shows the previous (stale) results. I attempted a fix in #6594, but after testing I realized it isn't that simple the root cause is how visibility guards are evaluated. Simply hiding rows until they're evaluated would make the menu slow to open. The proper fix i think is to make the evaluation fast caching/batching the expensive lookups. This probably affects many guarded rows beyond the two examples. https://github.com/user-attachments/assets/22df0266-c0af-4ee9-9166-392c25b04943
- 22df0266-c0af-4ee9-9166-392c25b04943
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
- Related PRpr/15048· confirmed
- Related PRpr/15049· confirmed
- Related PRpr/15042· confirmed
- Related PRpr/15039· confirmed
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.