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+O pop-out window exceeds the work area on 1440x900 logical displays
Reported by veer-y-singh · filed Sep 2, 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
Pressing SUPER+O to pop out a window creates a window taller than the monitor's usable work area. The top and bottom portions are clipped off-screen.
Steps to reproduce
- Use a display whose logical resolution is 1440x900 with the standard 26px Omarchy top bar.
- Open a tiled application such as Chromium.
- Press
SUPER+O. - Observe that the popped-out window extends beyond the available vertical work area.
Expected behavior
The popped-out window should remain fully visible within the active monitor's usable work area.
Actual behavior
omarchy-hyprland-window-pop uses a fixed default size of 1300x900:
width=${1:-1300}
height=${2:-900}This display is physically 2880x1800 at 2x scale, producing a 1440x900 logical desktop. Hyprland reports 26px reserved for the top bar, leaving only 874px of usable vertical space.
The command therefore requests a 900px-tall window in an 874px-tall work area. After centering, the top and bottom are clipped.
The default dimensions should be capped to the active monitor's usable work area, or calculated relative to that work area.
System details
- Dell XPS 14
- Intel Core Ultra X7 358H
- Intel Panther Lake Arc B390
- Omarchy 4.0.2-1
- Hyprland 0.56.2-1
- Internal display: 2880x1800 at 2x scale
- Logical display size: 1440x900
- Top reserved area: 26px
Screenshot
<img width="2880" height="1800" alt="Image" src="https://github.com/user-attachments/assets/33e590ec-ab0b-4b7d-a81b-96b574561ac9" />
View raw text
Pressing `SUPER+O` to pop out a window creates a window taller than the monitor's usable work area. The top and bottom portions are clipped off-screen.
### Steps to reproduce
1. Use a display whose logical resolution is 1440x900 with the standard 26px Omarchy top bar.
2. Open a tiled application such as Chromium.
3. Press `SUPER+O`.
4. Observe that the popped-out window extends beyond the available vertical work area.
### Expected behavior
The popped-out window should remain fully visible within the active monitor's usable work area.
### Actual behavior
`omarchy-hyprland-window-pop` uses a fixed default size of 1300x900:
```bash
width=${1:-1300}
height=${2:-900}
```
This display is physically 2880x1800 at 2x scale, producing a 1440x900 logical desktop. Hyprland reports 26px reserved for the top bar, leaving only 874px of usable vertical space.
The command therefore requests a 900px-tall window in an 874px-tall work area. After centering, the top and bottom are clipped.
The default dimensions should be capped to the active monitor's usable work area, or calculated relative to that work area.
### System details
- Dell XPS 14
- Intel Core Ultra X7 358H
- Intel Panther Lake Arc B390
- Omarchy 4.0.2-1
- Hyprland 0.56.2-1
- Internal display: 2880x1800 at 2x scale
- Logical display size: 1440x900
- Top reserved area: 26px
### Screenshot
<img width="2880" height="1800" alt="Image" src="https://github.com/user-attachments/assets/33e590ec-ab0b-4b7d-a81b-96b574561ac9" />- 33e590ec-ab0b-4b7d-a81b-96b574561ac9
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:32 UTC