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.
Feature request: mirror workspace bindings to numpad keycodes (KP1–KP0)
Reported by christianjgilman · filed Sep 5, 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
Problem
Workspace switching is bound to the digit row only (code:10–code:19 for workspaces 1–10). On keyboards with a numpad — very common as external boards — the numpad digits emit different keycodes and do nothing, even though users instinctively reach for them.
Proposal
Mirror the three existing variants (SUPER / SUPER+SHIFT / SUPER+SHIFT+ALT) onto the numpad keycodes inside the same loop in default/hypr/bindings/tiling.lua:
local numpad_codes = { [1]=87, [2]=88, [3]=89, [4]=83, [5]=84, [6]=85, [7]=79, [8]=80, [9]=81, [10]=90 }
for workspace = 1, 10 do
local key = "code:" .. numpad_codes[workspace]
o.bind("SUPER + " .. key, "Switch to workspace " .. workspace, hl.dsp.focus({ workspace = tostring(workspace) }))
o.bind("SUPER + SHIFT + " .. key, "Move window to workspace " .. workspace, hl.dsp.window.move({ workspace = tostring(workspace) }))
o.bind("SUPER + SHIFT + ALT + " .. key, "Move window silently to workspace " .. workspace, hl.dsp.window.move({ workspace = tostring(workspace), follow = false }))
end(xkb keycodes from /usr/share/X11/xkb/keycodes/evdev: KP1=87 … KP9=81, KP0=90.)
Notes
- Verified working on Hyprland 0.56.2 — user-added in
bindings.lua,hyprctl configerrorsclean, works regardless of NumLock state (keycode binds match the physical key). - ~20 extra bindings; names/descriptions render in
omarchy menu keybindings --printasSUPER + KP_END → Switch to workspace 1etc. - Happy to open a PR if this is welcome.
View raw text
### Problem
Workspace switching is bound to the digit row only (`code:10`–`code:19` for workspaces 1–10). On keyboards with a numpad — very common as external boards — the numpad digits emit different keycodes and **do nothing**, even though users instinctively reach for them.
### Proposal
Mirror the three existing variants (SUPER / SUPER+SHIFT / SUPER+SHIFT+ALT) onto the numpad keycodes inside the same loop in `default/hypr/bindings/tiling.lua`:
```lua
local numpad_codes = { [1]=87, [2]=88, [3]=89, [4]=83, [5]=84, [6]=85, [7]=79, [8]=80, [9]=81, [10]=90 }
for workspace = 1, 10 do
local key = "code:" .. numpad_codes[workspace]
o.bind("SUPER + " .. key, "Switch to workspace " .. workspace, hl.dsp.focus({ workspace = tostring(workspace) }))
o.bind("SUPER + SHIFT + " .. key, "Move window to workspace " .. workspace, hl.dsp.window.move({ workspace = tostring(workspace) }))
o.bind("SUPER + SHIFT + ALT + " .. key, "Move window silently to workspace " .. workspace, hl.dsp.window.move({ workspace = tostring(workspace), follow = false }))
end
```
(xkb keycodes from `/usr/share/X11/xkb/keycodes/evdev`: KP1=87 … KP9=81, KP0=90.)
### Notes
- Verified working on Hyprland 0.56.2 — user-added in `bindings.lua`, `hyprctl configerrors` clean, works regardless of NumLock state (keycode binds match the physical key).
- ~20 extra bindings; names/descriptions render in `omarchy menu keybindings --print` as `SUPER + KP_END → Switch to workspace 1` etc.
- Happy to open a PR if this is welcome.
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:53 UTC