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

Pinned pop-out window remains foreground across workspaces and obscures other windows

Reported by tufi · filed Sep 16, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 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

Pinned pop-out window remains foreground across workspaces and obscures other windowsrevision 1 · captured 2026-09-28 21:23 UTC via poll

Pinned pop-out window remains foreground across workspaces and obscures other windows

Environment

  • Omarchy: 4.0.3-1
  • Kernel: 7.2.3-arch1-3 x86_64
  • Session: Wayland/Hyprland (WAYLAND_DISPLAY=wayland-1)

What happened

After using the Omarchy window shortcuts, a floating window became pinned and remained in the foreground across every workspace. It obscured newly opened windows, including a terminal, and made the other windows appear to have disappeared. Alt+Tab did not reveal the other windows while on workspace 1.

The behavior was difficult to recover from because the shortcuts have overlapping effects:

  • Super+0 switched workspaces while the pinned window remained visible.
  • Super+O (pop-out) made the window large, floating, pinned, and always on top.
  • Super+T changed floating/tiling but did not remove the pin.

Even after trying Super+O again, the behavior was not clear; a second floating terminal became visible while the original window continued to obscure the workspace. The user could not determine where the other windows had gone.

Expected behavior

There should be an obvious, reliable way to unpin or lower a pop-out window. A pinned window should not obscure newly opened windows without a clear on-screen indication, and the pop-out shortcut should have an unambiguous undo behavior.

Steps to reproduce

  1. Open multiple windows on a workspace.
  2. Open or focus a floating window.
  3. Use the Omarchy pop-out shortcut (Super+O).
  4. Switch workspaces with Super+0 and open another terminal with Super+Enter.
  5. Observe that the pop-out remains in the foreground on every workspace and obscures the new terminal and other windows.
  6. Try Alt+Tab, Super+T, and Super+O to recover; the resulting state is not apparent to the user.

Additional diagnostic issue

The command advertised by omarchy --help as omarchy debug is not routable on this installation: omarchy debug --no-sudo --print returns Unknown Omarchy command. Please document the current diagnostic command or fix the command route.

Diagnostics

omarchy version:

4.0.3-1

The compositor socket was not reachable from the diagnostic environment, so hyprctl clients could not be collected.

View raw text
# Pinned pop-out window remains foreground across workspaces and obscures other windows

## Environment

- Omarchy: `4.0.3-1`
- Kernel: `7.2.3-arch1-3 x86_64`
- Session: Wayland/Hyprland (`WAYLAND_DISPLAY=wayland-1`)

## What happened

After using the Omarchy window shortcuts, a floating window became pinned and remained in the foreground across every workspace. It obscured newly opened windows, including a terminal, and made the other windows appear to have disappeared. `Alt+Tab` did not reveal the other windows while on workspace 1.

The behavior was difficult to recover from because the shortcuts have overlapping effects:

- `Super+0` switched workspaces while the pinned window remained visible.
- `Super+O` (pop-out) made the window large, floating, pinned, and always on top.
- `Super+T` changed floating/tiling but did not remove the pin.

Even after trying `Super+O` again, the behavior was not clear; a second floating terminal became visible while the original window continued to obscure the workspace. The user could not determine where the other windows had gone.

## Expected behavior

There should be an obvious, reliable way to unpin or lower a pop-out window. A pinned window should not obscure newly opened windows without a clear on-screen indication, and the pop-out shortcut should have an unambiguous undo behavior.

## Steps to reproduce

1. Open multiple windows on a workspace.
2. Open or focus a floating window.
3. Use the Omarchy pop-out shortcut (`Super+O`).
4. Switch workspaces with `Super+0` and open another terminal with `Super+Enter`.
5. Observe that the pop-out remains in the foreground on every workspace and obscures the new terminal and other windows.
6. Try `Alt+Tab`, `Super+T`, and `Super+O` to recover; the resulting state is not apparent to the user.

## Additional diagnostic issue

The command advertised by `omarchy --help` as `omarchy debug` is not routable on this installation: `omarchy debug --no-sudo --print` returns `Unknown Omarchy command`. Please document the current diagnostic command or fix the command route.

## Diagnostics

`omarchy version`:

```text
4.0.3-1
```

The compositor socket was not reachable from the diagnostic environment, so `hyprctl clients` could not be collected.

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 14:27 UTC