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+J runs dwindle-only togglesplit on scrolling workspaces
Reported by AvrumFeldman · filed Aug 19, 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
Lenovo ThinkPad X13 Gen 2i; Intel Core i5-1145G7; Intel Iris Xe; Omarchy 4.0.0-1; Hyprland 0.56.2; kernel 7.1.8-arch1-3.
What's wrong?
Omarchy's stock SUPER + J binding always sends the dwindle-only togglesplit layout message:
o.bind("SUPER + J", "Toggle window split", hl.dsp.layout("togglesplit"))The stock SUPER + L binding can switch an individual workspace to the scrolling layout. Once a workspace is using scrolling, pressing SUPER + J produces a Lua runtime-error popup saying there is no such layout message for scrolling.
Steps to reproduce:
- Use the stock Omarchy Hyprland bindings.
- Press
SUPER + Lto switch the active workspace to the scrolling layout. - Press
SUPER + J. - Observe the runtime error:
no such layoutmsg for scrolling.
Expected: a stock shortcut should not produce a Lua runtime error on a layout enabled by another stock shortcut. It could dispatch a scrolling equivalent, such as consume_or_expel prev, or safely do nothing outside dwindle.
The failing binding is currently in /usr/share/omarchy/default/hypr/bindings/tiling.lua. A working local workaround is to inspect hl.get_active_workspace().tiled_layout and dispatch togglesplit only for dwindle, with a scrolling-specific action for scrolling.
I searched the Omarchy issue tracker for scrolling, SUPER+J, layoutmsg, and togglesplit before filing and did not find a report for this behavior.
View raw text
### System details
Lenovo ThinkPad X13 Gen 2i; Intel Core i5-1145G7; Intel Iris Xe; Omarchy 4.0.0-1; Hyprland 0.56.2; kernel 7.1.8-arch1-3.
### What's wrong?
Omarchy's stock `SUPER + J` binding always sends the dwindle-only `togglesplit` layout message:
```lua
o.bind("SUPER + J", "Toggle window split", hl.dsp.layout("togglesplit"))
```
The stock `SUPER + L` binding can switch an individual workspace to the scrolling layout. Once a workspace is using scrolling, pressing `SUPER + J` produces a Lua runtime-error popup saying there is no such layout message for scrolling.
Steps to reproduce:
1. Use the stock Omarchy Hyprland bindings.
2. Press `SUPER + L` to switch the active workspace to the scrolling layout.
3. Press `SUPER + J`.
4. Observe the runtime error: `no such layoutmsg for scrolling`.
Expected: a stock shortcut should not produce a Lua runtime error on a layout enabled by another stock shortcut. It could dispatch a scrolling equivalent, such as `consume_or_expel prev`, or safely do nothing outside dwindle.
The failing binding is currently in `/usr/share/omarchy/default/hypr/bindings/tiling.lua`. A working local workaround is to inspect `hl.get_active_workspace().tiled_layout` and dispatch `togglesplit` only for dwindle, with a scrolling-specific action for scrolling.
I searched the Omarchy issue tracker for scrolling, SUPER+J, layoutmsg, and togglesplit before filing and did not find a report for this behavior.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 04:49 UTC