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.
[hyprland] Steam main window defaults to small floating 1100x700 instead of tiled/maximizable
Reported by 0xMax-Sec · filed Aug 30, 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
Summary
In Omarchy 4, the default Hyprland window rules force the main Steam client window to float at a fixed size of 1100x700, while suppress_event = "maximize" is globally configured in windows.lua. This causes Steam's main store/library window to feel cramped on high-DPI/larger displays, and clicking the CSD maximize button inside the Steam client fails to maximize the window.
Current Implementation
In /usr/share/omarchy/default/hypr/apps/steam.lua:
o.window("steam", { float = true, idle_inhibit = "fullscreen" })
o.window({ class = "steam", title = "Steam" }, { center = true, size = { 1100, 700 } })And in /usr/share/omarchy/default/hypr/windows.lua:
o.window(".*", { suppress_event = "maximize" })Problem
Because Steam runs under XWayland with custom Client-Side Decorations (CSD), clicking the maximize button within Steam's title bar does nothing, and the initial 1100x700 geometry leaves the store and library narrow with large black borders unless the user manually invokes SUPER + F or overrides the rule in ~/.config/hypr/hyprland.lua.
Proposed Solution
Allow the main Steam client (title = "^Steam$") to default to tiled mode (tile = true) or provide an easy toggle, while keeping auxiliary popups and the Friends List floating:
o.window("steam", { float = true, idle_inhibit = "fullscreen" })
o.window({ class = "steam", title = "^Steam$" }, { tile = true })
o.window({ class = "steam", title = "Friends List" }, { size = { 460, 800 }, float = true })View raw text
### Summary
In Omarchy 4, the default Hyprland window rules force the main Steam client window to float at a fixed size of `1100x700`, while `suppress_event = "maximize"` is globally configured in `windows.lua`. This causes Steam's main store/library window to feel cramped on high-DPI/larger displays, and clicking the CSD maximize button inside the Steam client fails to maximize the window.
### Current Implementation
In `/usr/share/omarchy/default/hypr/apps/steam.lua`:
```lua
o.window("steam", { float = true, idle_inhibit = "fullscreen" })
o.window({ class = "steam", title = "Steam" }, { center = true, size = { 1100, 700 } })
```
And in `/usr/share/omarchy/default/hypr/windows.lua`:
```lua
o.window(".*", { suppress_event = "maximize" })
```
### Problem
Because Steam runs under XWayland with custom Client-Side Decorations (CSD), clicking the maximize button within Steam's title bar does nothing, and the initial 1100x700 geometry leaves the store and library narrow with large black borders unless the user manually invokes `SUPER + F` or overrides the rule in `~/.config/hypr/hyprland.lua`.
### Proposed Solution
Allow the main Steam client (`title = "^Steam$"`) to default to tiled mode (`tile = true`) or provide an easy toggle, while keeping auxiliary popups and the Friends List floating:
```lua
o.window("steam", { float = true, idle_inhibit = "fullscreen" })
o.window({ class = "steam", title = "^Steam$" }, { tile = true })
o.window({ class = "steam", title = "Friends List" }, { size = { 460, 800 }, float = true })
```
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:11 UTC