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: Optional GNOME-style multi-monitor workspaces
Reported by enriquemorenotent · filed Aug 23, 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
It would be useful to have an optional setting for GNOME-style workspace behavior on multi-monitor setups.
Currently, Hyprland/Omarchy treats workspaces independently per monitor. This means one monitor can be on workspace 1 while another is on workspace 5, and switching workspaces only affects the currently focused monitor.
For some workflows, it makes more sense for a workspace to represent a complete context across all monitors.
For example:
- Workspace 1 = Project A
- Left monitor: documentation/browser
- Center monitor: editor
- Right monitor: terminal/logs
- Workspace 2 = Project B
- Workspace 3 = Personal
In that model, switching from workspace 1 to workspace 2 should switch all monitors together, preserving a complete multi-monitor layout for each workspace.
GNOME calls this behavior "Workspaces on all displays".
I am not suggesting this should replace the current behavior or become the default. It would be great to simply have a toggle/config option such as:
- Independent workspaces per monitor (current behavior)
- Workspaces spanning all monitors
This would make Omarchy much more comfortable for users who treat workspaces as semantic contexts rather than independent desktops attached to individual monitors.
If this cannot reasonably be implemented at the Omarchy level and requires upstream Hyprland support, it would also be useful to know that.
View raw text
It would be useful to have an optional setting for GNOME-style workspace behavior on multi-monitor setups. Currently, Hyprland/Omarchy treats workspaces independently per monitor. This means one monitor can be on workspace 1 while another is on workspace 5, and switching workspaces only affects the currently focused monitor. For some workflows, it makes more sense for a workspace to represent a complete context across all monitors. For example: - Workspace 1 = Project A - Left monitor: documentation/browser - Center monitor: editor - Right monitor: terminal/logs - Workspace 2 = Project B - Workspace 3 = Personal In that model, switching from workspace 1 to workspace 2 should switch all monitors together, preserving a complete multi-monitor layout for each workspace. GNOME calls this behavior "Workspaces on all displays". I am not suggesting this should replace the current behavior or become the default. It would be great to simply have a toggle/config option such as: - Independent workspaces per monitor (current behavior) - Workspaces spanning all monitors This would make Omarchy much more comfortable for users who treat workspaces as semantic contexts rather than independent desktops attached to individual monitors. If this cannot reasonably be implemented at the Omarchy level and requires upstream Hyprland support, it would also be useful to know that.
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 08:33 UTC