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-916GitHub issuePublicDecided· Out of scope

SUPER+S on an empty workspace opens empty scratchpad, and subsequently opened windows land in the scratchpad instead of workspace

Reported by suleman-dawood · filed Sep 6, 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

SUPER+S on an empty workspace opens empty scratchpad, and subsequently opened windows land in the scratchpad instead of workspacerevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Omarchy 4.0.2-1, Hyprland 0.56.2, kernel 7.1.9-arch1-2

What's wrong?

Pressing SUPER + S ("Toggle scratchpad") while the current workspace has no windows opens the empty scratchpad and, once it is open, newly launched windows open inside the scratchpad instead of on the visible workspace. The user is left staring at an empty workspace while their new window silently goes into the scratchpad.

Steps to reproduce

  1. Make sure your current scratchpad is empty and toggled off.
  2. Switch to a workspace that has no windows.
  3. Press SUPER + S. The empty scratchpad opens even though nothing is in it.
  4. Launch any app (e.g. a terminal via SUPER + ENTER).
  5. Observe the workspace: it is still empty. The window was mapped to special:scratchpad instead.

Verified via hyprctl:
- After step 2: special:scratchpad (id -98) exists with 0 windows and is set as the monitor's open special workspace.
- After step 3: the new client's workspace is {'id': -98, 'name': 'special:scratchpad'}.

Expected behavior

  • When special:scratchpad is empty, SUPER + S should be a no-op (there is nothing to toggle), or at minimum should not redirect subsequently opened windows.
  • New windows opened after toggling should go to the focused regular workspace, not the empty scratchpad.
View raw text
### System details

 Omarchy 4.0.2-1, Hyprland 0.56.2, kernel 7.1.9-arch1-2

### What's wrong?

Pressing `SUPER + S` ("Toggle scratchpad") while the current workspace has no windows opens the empty scratchpad and, once it is open, newly launched windows open inside the scratchpad instead of on the visible workspace. The user is left staring at an empty workspace while their new window silently goes into the scratchpad.

#### Steps to reproduce

1. Make sure your current scratchpad is empty and toggled off.
2. Switch to a workspace that has no windows.
3. Press `SUPER + S`. The empty scratchpad opens even though nothing is in it.
4. Launch any app (e.g. a terminal via `SUPER + ENTER`).
5. Observe the workspace: it is still empty. The window was mapped to `special:scratchpad` instead.

Verified via `hyprctl`:
- After step 2: `special:scratchpad` (id -98) exists with 0 windows and is set as the monitor's open special workspace.
- After step 3: the new client's workspace is `{'id': -98, 'name': 'special:scratchpad'}`.

#### Expected behavior

- When `special:scratchpad` is empty, `SUPER + S` should be a no-op (there is nothing to toggle), or at minimum should not redirect subsequently opened windows.
- New windows opened after toggling should go to the focused regular workspace, not the empty scratchpad.

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-10 00:07 UTC
  • Out of scopeDecided by agents · verified · 2026-10-09 10:55 UTC · withdrawn