Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1635GitHub issuePublicDecided· Out of scope

Notifications: toast popups appear on all monitors simultaneously

Reported by Deoxizn · filed Aug 20, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 days ago.

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

Notifications: toast popups appear on all monitors simultaneouslyrevision 1 · captured 2026-09-28 21:29 UTC via poll

Problem

On multi-monitor setups, notification toast popups appear on every connected output simultaneously. The same notification card is duplicated on each screen.

Root cause

In omarchy.notifications Service.qml, the toast popup window is created for all outputs via:

Variants {
    model: Quickshell.screens  // one PanelWindow per output
    PanelWindow {
        screen: modelData
        Repeater { model: popupModel }  // shared model, no per-screen filter
    }
}

Every PanelWindow renders from the same shared popupModel, so each monitor shows identical toasts.

Suggested fix

Add a configurable primary output (or default to the focused/hyprland primary monitor), and only render toasts on that screen. Could be:

  1. A shell.toml option like notifications.output = DP-1
  2. Or default to Hyprland.primaryMonitor / first screen in Quickshell.screens

The change would be \~5 lines: skip creating the PanelWindow for non-primary outputs, or filter the Repeater model per screen.

Use case

Dual-monitor users typically want notifications consolidated on one display rather than duplicated across all screens.

View raw text
## Problem

On multi-monitor setups, notification toast popups appear on every connected output simultaneously. The same notification card is duplicated on each screen.

## Root cause

In `omarchy.notifications` `Service.qml`, the toast popup window is created for all outputs via:

```qml
Variants {
    model: Quickshell.screens  // one PanelWindow per output
    PanelWindow {
        screen: modelData
        Repeater { model: popupModel }  // shared model, no per-screen filter
    }
}
```

Every PanelWindow renders from the same shared `popupModel`, so each monitor shows identical toasts.

## Suggested fix

Add a configurable primary output (or default to the focused/hyprland primary monitor), and only render toasts on that screen. Could be:

1. A `shell.toml` option like `notifications.output = DP-1`
2. Or default to `Hyprland.primaryMonitor` / first screen in `Quickshell.screens`

The change would be \~5 lines: skip creating the PanelWindow for non-primary outputs, or filter the Repeater model per screen.

## Use case

Dual-monitor users typically want notifications consolidated on one display rather than duplicated across all screens.

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

  • Related PRpr/9928· confirmed

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:51 UTC