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

Feature: window layout snapshots (save and restore workspace arrangements)

Reported by chiang21fcb · filed Aug 27, 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

Feature: window layout snapshots (save and restore workspace arrangements)revision 1 · captured 2026-09-28 21:24 UTC via poll

Problem

When switching between different tasks (coding, writing, browsing, gaming), I manually rearrange windows across workspaces. Each time I come back to a task, I spend time recreating the same layout. A layout snapshot would let me save and restore these arrangements with a single command.

Proposed solution

A new omarchy layout CLI command:

omarchy layout save coding     # Save current window positions as "coding"
omarchy layout restore coding  # Restore the "coding" layout
omarchy layout list            # List saved layouts
omarchy layout delete coding   # Delete a saved layout

Each layout snapshot records:
- Which workspace each window is on
- Window position and size
- Window class/app identifier

How it works

Uses hyprctl (already used by Omarchy for window management) to capture and restore window state. Layouts stored as JSON files in ~/.config/omarchy/layouts/.

Why this fits Omarchy

Omarchy is opinionated about productivity. A layout snapshot system makes the desktop feel more intentional: define your workspaces once, switch between them instantly. It pairs well with the existing hotkey system and the top bar Trigger menu.

Scope

  • CLI-only for the initial version
  • No auto-launching of missing apps
  • Hyprland-only (Omarchy default)
View raw text
## Problem

When switching between different tasks (coding, writing, browsing, gaming), I manually rearrange windows across workspaces. Each time I come back to a task, I spend time recreating the same layout. A layout snapshot would let me save and restore these arrangements with a single command.

## Proposed solution

A new `omarchy layout` CLI command:

```bash
omarchy layout save coding     # Save current window positions as "coding"
omarchy layout restore coding  # Restore the "coding" layout
omarchy layout list            # List saved layouts
omarchy layout delete coding   # Delete a saved layout
```

Each layout snapshot records:
- Which workspace each window is on
- Window position and size
- Window class/app identifier

## How it works

Uses `hyprctl` (already used by Omarchy for window management) to capture and restore window state. Layouts stored as JSON files in `~/.config/omarchy/layouts/`.

## Why this fits Omarchy

Omarchy is opinionated about productivity. A layout snapshot system makes the desktop feel more intentional: define your workspaces once, switch between them instantly. It pairs well with the existing hotkey system and the top bar Trigger menu.

## Scope

- CLI-only for the initial version
- No auto-launching of missing apps
- Hyprland-only (Omarchy default)

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/10373· confirmed
  • Related PRpr/11454· 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 09:28 UTC