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.
windowrule opacity: active-state "override" has no effect when loaded from config (reload), only when injected live via hyprctl eval
Reported by granite4lyfe · filed Aug 31, 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
What happened
A windowrule that sets active-state opacity to 1.0 override (fully opaque
when focused) has no visible effect when it's loaded from a Lua config file
via hyprctl reload, even though the identical rule injected live viahyprctl eval fixes it immediately. This holds for both tag: and class:
matches — it's not about which match type is used, it's specifically about
the file+reload path vs. live eval.
Inactive-state override (0.96 override) works correctly either way — only
the active state is affected.
Expected
A windowrule loaded from config via hyprctl reload should behave the same
as the identical rule applied live via hyprctl eval.
Steps to reproduce
- In
~/.config/hypr/windows.lua(Omarchy's Lua config layer), add:
o.window({ class = "<some app class>" }, { opacity = "1.0 override 0.96 override" })
(Omarchy's own default rule already tags all windows and applies
opacity 0.985 0.96 via tag:default-opacity —
/usr/share/omarchy/default/hypr/windows.lua — so any window will show
some transparency by default; this rule is meant to force full opacity
on top of that.)
2. hyprctl reload, then hyprctl configerrors (clean, no errors).
3. Open a completely fresh instance of that app (not one that was already
open before step 1/2). Focus it — wallpaper is still visibly bleeding
through. Unfocus it — the 0.96 override does correctly apply (dims as
expected).
4. Now run the identical rule live instead:
hyprctl eval 'hl.window_rule({match = {class = "<same app class>"}, opacity = "1.0 override 0.96 override"})'
— this applies correctly and immediately on the same window, both states.
Tested clean on multiple fresh windows (Nautilus, a fresh foot terminal)
with no other opacity rules touching them, before and after omarchy update
(4.0.1-1 → 4.0.2-1) — same result every time. Tested with both tag: andclass: match types in the file — both fail the same way; only the eval
path works.
System
- Omarchy 4.0.2-1
- Hyprland 0.56.2
- Kernel 7.1.9-arch1-2
- GPU: AMD Radeon RX 9070 XT (amdgpu, RDNA-4)
- Display: Wayland, Hyprland compositor, XWayland 24.1.13
Screenshot
Attached below — a focused Nautilus window with the wallpaper visibly
showing through despite the override rule.
View raw text
## What happened
A windowrule that sets active-state opacity to `1.0 override` (fully opaque
when focused) has no visible effect when it's loaded from a Lua config file
via `hyprctl reload`, even though the identical rule injected live via
`hyprctl eval` fixes it immediately. This holds for both `tag:` and `class:`
matches — it's not about which match type is used, it's specifically about
the file+reload path vs. live eval.
Inactive-state override (`0.96 override`) works correctly either way — only
the active state is affected.
## Expected
A windowrule loaded from config via `hyprctl reload` should behave the same
as the identical rule applied live via `hyprctl eval`.
## Steps to reproduce
1. In `~/.config/hypr/windows.lua` (Omarchy's Lua config layer), add:
`o.window({ class = "<some app class>" }, { opacity = "1.0 override 0.96 override" })`
(Omarchy's own default rule already tags all windows and applies
`opacity 0.985 0.96` via `tag:default-opacity` —
`/usr/share/omarchy/default/hypr/windows.lua` — so any window will show
*some* transparency by default; this rule is meant to force full opacity
on top of that.)
2. `hyprctl reload`, then `hyprctl configerrors` (clean, no errors).
3. Open a completely fresh instance of that app (not one that was already
open before step 1/2). Focus it — wallpaper is still visibly bleeding
through. Unfocus it — the 0.96 override *does* correctly apply (dims as
expected).
4. Now run the identical rule live instead:
`hyprctl eval 'hl.window_rule({match = {class = "<same app class>"}, opacity = "1.0 override 0.96 override"})'`
— this applies correctly and immediately on the same window, both states.
Tested clean on multiple fresh windows (Nautilus, a fresh `foot` terminal)
with no other opacity rules touching them, before and after `omarchy update`
(4.0.1-1 → 4.0.2-1) — same result every time. Tested with both `tag:` and
`class:` match types in the file — both fail the same way; only the eval
path works.
## System
- Omarchy 4.0.2-1
- Hyprland 0.56.2
- Kernel 7.1.9-arch1-2
- GPU: AMD Radeon RX 9070 XT (amdgpu, RDNA-4)
- Display: Wayland, Hyprland compositor, XWayland 24.1.13
## Screenshot
Attached below — a focused Nautilus window with the wallpaper visibly
showing through despite the override rule.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 10:21 UTC