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

[restart app] Preserve workspace, group, and position when relaunching an application

Reported by nojaf · filed Sep 8, 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

[restart app] Preserve workspace, group, and position when relaunching an applicationrevision 1 · captured 2026-09-28 21:23 UTC via poll

Problem

omarchy restart app <application-name> kills the application and relaunches it, but the replacement window is not restored to the original Hyprland placement.

For example, I ran:

omarchy restart app t3code

The original T3 Code window was positioned in a specific workspace layout, outside a window group on the left. After the restart, the replacement window opened inside a different group instead of returning to the original location.

Expected behavior

Restarting an application should preserve, where possible:

  • Workspace
  • Monitor
  • Tiling position
  • Group membership or non-membership
  • Relative position in the layout

At minimum, the command should document that placement is not preserved, or provide an option to restore it.

Environment

  • Omarchy: 4.0.2-1
  • Hyprland: 0.56.2-1
  • Application: t3code-bin 0.0.39-1
  • Session: Hyprland on Wayland

Additional context

The current restart helper kills the process and launches it again through uwsm-app. It does not appear to capture the original window state before killing the application. A possible implementation could capture the matching client from hyprctl clients -j, restart the application, then apply workspace/group/focus placement once the replacement window appears.

View raw text
### Problem

`omarchy restart app <application-name>` kills the application and relaunches it, but the replacement window is not restored to the original Hyprland placement.

For example, I ran:

```bash
omarchy restart app t3code
```

The original T3 Code window was positioned in a specific workspace layout, outside a window group on the left. After the restart, the replacement window opened inside a different group instead of returning to the original location.

### Expected behavior

Restarting an application should preserve, where possible:

- Workspace
- Monitor
- Tiling position
- Group membership or non-membership
- Relative position in the layout

At minimum, the command should document that placement is not preserved, or provide an option to restore it.

### Environment

- Omarchy: `4.0.2-1`
- Hyprland: `0.56.2-1`
- Application: `t3code-bin 0.0.39-1`
- Session: Hyprland on Wayland

### Additional context

The current restart helper kills the process and launches it again through `uwsm-app`. It does not appear to capture the original window state before killing the application. A possible implementation could capture the matching client from `hyprctl clients -j`, restart the application, then apply workspace/group/focus placement once the replacement window appears.

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 11:08 UTC