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.
Super+Alt+number shows an error for unavailable group windows
Reported by nojaf · filed Sep 16, 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
- Omarchy: 4.0.4-1
- Hyprland: 0.56.2
What is wrong?
The default group-window number bindings show an error notification when the selected index does not exist.
Steps to reproduce
- Create a group containing two windows.
- Press
Super+Alt+3. - Observe the notification:
Runtime error in lua: Index out of range
Expected behavior
Pressing a number for a group window that does not exist should do nothing and should not display an error notification.
Actual behavior
The default binding in default/hypr/bindings/tiling.lua binds group indices 1 through 5 unconditionally:
for index = 1, 5 do
o.bind("SUPER + ALT + code:" .. tostring(index + 9), "Switch to group window " .. index, hl.dsp.group.active({ index = index }))
endHyprland correctly rejects the unavailable index, but Omarchy displays the returned dispatcher error as a Lua runtime notification. This happens, for example, with Super+Alt+3 when the group has only two windows.
The binding could guard against the current group size, or unavailable indices could be treated as no-ops.
Related, but different: #4832 concerned numeric group selection being off by one and was attributed to Hyprland.
View raw text
## System details
- Omarchy: 4.0.4-1
- Hyprland: 0.56.2
## What is wrong?
The default group-window number bindings show an error notification when the selected index does not exist.
### Steps to reproduce
1. Create a group containing two windows.
2. Press `Super+Alt+3`.
3. Observe the notification:
`Runtime error in lua: Index out of range`
### Expected behavior
Pressing a number for a group window that does not exist should do nothing and should not display an error notification.
### Actual behavior
The default binding in `default/hypr/bindings/tiling.lua` binds group indices 1 through 5 unconditionally:
```lua
for index = 1, 5 do
o.bind("SUPER + ALT + code:" .. tostring(index + 9), "Switch to group window " .. index, hl.dsp.group.active({ index = index }))
end
```
Hyprland correctly rejects the unavailable index, but Omarchy displays the returned dispatcher error as a Lua runtime notification. This happens, for example, with `Super+Alt+3` when the group has only two windows.
The binding could guard against the current group size, or unavailable indices could be treated as no-ops.
Related, but different: #4832 concerned numeric group selection being off by one and was attributed to Hyprland.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
- Fixed bypr/12155· 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.
- Out of scopeDecided by agents · verified · 2026-10-09 14:13 UTC