Proof Portal

Sign in
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-479GitHub issuePublicDecided· Out of scope

Alt+Tab does not follow adjacent windows in scrolling layout

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

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

Alt+Tab does not follow adjacent windows in scrolling layoutrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

AMD Ryzen 7 5800H, NVIDIA RTX 3050 Ti + AMD Radeon Vega, x86_64, Omarchy 4.0.3-1, Hyprland 0.56.2

What's wrong?

In a scrolling-layout workspace, Alt+Tab uses cycle_next, whose internal window order can differ from the visible left-to-right order of the scrolling tape. As a result, repeatedly pressing Alt+Tab can skip the window immediately to the right and appear to jump around.

Steps to reproduce:

  1. Toggle a workspace to scrolling layout with Super+L.
  2. Open at least four tiled windows and rearrange them so their visual order differs from their creation/focus order.
  3. Press Alt+Tab repeatedly.
  4. Observe that focus does not consistently move to the adjacent window on the right.

Expected behavior:

  • In scrolling layout, Alt+Tab focuses the adjacent tiled window to the right.
  • Alt+Shift+Tab focuses the adjacent tiled window to the left.
  • Dwindle workspaces and floating windows retain the current cycle_next behavior.

This is related to, but separate from, #7561. That issue concerns reverse cycling becoming stuck between two windows because bring_to_top affects cycle order. This issue is about making Alt+Tab follow visual adjacency specifically in scrolling layout.

Related Hyprland discussion: https://github.com/hyprwm/Hyprland/discussions/13951

View raw text
### System details

AMD Ryzen 7 5800H, NVIDIA RTX 3050 Ti + AMD Radeon Vega, x86_64, Omarchy 4.0.3-1, Hyprland 0.56.2

### What's wrong?

In a scrolling-layout workspace, `Alt+Tab` uses `cycle_next`, whose internal window order can differ from the visible left-to-right order of the scrolling tape. As a result, repeatedly pressing `Alt+Tab` can skip the window immediately to the right and appear to jump around.

Steps to reproduce:

1. Toggle a workspace to scrolling layout with `Super+L`.
2. Open at least four tiled windows and rearrange them so their visual order differs from their creation/focus order.
3. Press `Alt+Tab` repeatedly.
4. Observe that focus does not consistently move to the adjacent window on the right.

Expected behavior:

- In scrolling layout, `Alt+Tab` focuses the adjacent tiled window to the right.
- `Alt+Shift+Tab` focuses the adjacent tiled window to the left.
- Dwindle workspaces and floating windows retain the current `cycle_next` behavior.

This is related to, but separate from, #7561. That issue concerns reverse cycling becoming stuck between two windows because `bring_to_top` affects cycle order. This issue is about making Alt+Tab follow visual adjacency specifically in scrolling layout.

Related Hyprland discussion: https://github.com/hyprwm/Hyprland/discussions/13951

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