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.
Regression: Quickshell workspace indicator shows globally focused workspace on every monitor
Reported by NeroSong · filed Aug 25, 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
AMD Ryzen 5 7640HS with Radeon 760M (Phoenix1), Omarchy 4.0.0-1, Hyprland, two displays (eDP-1 + DP-1)
What's wrong?
Description
On a multi-monitor setup, the built-in Quickshell omarchy.workspaces widget highlights the globally focused Hyprland workspace on every monitor's bar instead of the active workspace of that specific monitor.
The actual Hyprland workspace assignment works correctly: switching the laptop display does not change the content on the external display. Only the indicator on the external display changes, so it no longer represents what that monitor is showing.
This appears to be a regression of #1533 after the migration from Waybar to the Quickshell-based Omarchy Shell. Issue #1533 was closed as completed, but the same behavior is present in the current widget.
Steps to reproduce
- Connect an external monitor and keep the Omarchy bar visible on both displays.
- Put workspace 5 on the external display.
- Focus the laptop display and switch it to workspace 3.
- Observe the workspace indicator on the external display.
Actual behavior
Both bars highlight workspace 3, even though the external display still shows workspace 5.
Expected behavior
- The laptop display bar should highlight workspace 3.
- The external display bar should continue highlighting workspace 5.
- Each bar should derive its active workspace from the monitor associated with that bar.
Verified Hyprland state
While reproducing the issue, hyprctl monitors reported:
eDP-1: active workspace 3DP-1: active workspace 5
The visible content matched that state.
Suspected cause
The packaged shell/plugins/bar/widgets/Workspaces.qml determines the focused state using the global workspace:
readonly property bool focused:
Hyprland.focusedWorkspace !== null &&
Hyprland.focusedWorkspace.id === modelDataEvery bar instance therefore reads the same Hyprland.focusedWorkspace, regardless of which screen owns that bar.
Diagnostics
The installed Omarchy version is 4.0.0-1. This release does not expose the documented omarchy debug --no-sudo --print command; it returns Unknown Omarchy command, so no debug output is attached.
View raw text
### System details
AMD Ryzen 5 7640HS with Radeon 760M (Phoenix1), Omarchy 4.0.0-1, Hyprland, two displays (eDP-1 + DP-1)
### What's wrong?
## Description
On a multi-monitor setup, the built-in Quickshell `omarchy.workspaces` widget highlights the globally focused Hyprland workspace on every monitor's bar instead of the active workspace of that specific monitor.
The actual Hyprland workspace assignment works correctly: switching the laptop display does not change the content on the external display. Only the indicator on the external display changes, so it no longer represents what that monitor is showing.
This appears to be a regression of #1533 after the migration from Waybar to the Quickshell-based Omarchy Shell. Issue #1533 was closed as completed, but the same behavior is present in the current widget.
## Steps to reproduce
1. Connect an external monitor and keep the Omarchy bar visible on both displays.
2. Put workspace 5 on the external display.
3. Focus the laptop display and switch it to workspace 3.
4. Observe the workspace indicator on the external display.
## Actual behavior
Both bars highlight workspace 3, even though the external display still shows workspace 5.
## Expected behavior
- The laptop display bar should highlight workspace 3.
- The external display bar should continue highlighting workspace 5.
- Each bar should derive its active workspace from the monitor associated with that bar.
## Verified Hyprland state
While reproducing the issue, `hyprctl monitors` reported:
- `eDP-1`: active workspace 3
- `DP-1`: active workspace 5
The visible content matched that state.
## Suspected cause
The packaged `shell/plugins/bar/widgets/Workspaces.qml` determines the focused state using the global workspace:
```qml
readonly property bool focused:
Hyprland.focusedWorkspace !== null &&
Hyprland.focusedWorkspace.id === modelData
```
Every bar instance therefore reads the same `Hyprland.focusedWorkspace`, regardless of which screen owns that bar.
## Diagnostics
The installed Omarchy version is `4.0.0-1`. This release does not expose the documented `omarchy debug --no-sudo --print` command; it returns `Unknown Omarchy command`, so no debug output is attached.
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:43 UTC