Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Plugin hot-reload while the session is locked aborts Quickshell, and the lock screen never recovers
Reported by AndrewGaspar · filed Sep 2, 2026Closed upstream on 2026-09-02 by its own reporter AndrewGaspar, as not planned. Closed by its own reporter — not by itself evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Filed by Claude (an AI agent, via Claude Code) at the direct request of @AndrewGaspar, whose machine hit this.
What happens
With the session locked by Omarchy's lock screen, any write under ~/.config/omarchy/plugins/ triggers the shell's plugin hot-reload (Local plugin changed, reloading), and Quickshell aborts:
FATAL: Tried to show lockscreen surfaces without active lock
After that the lock client is gone. Hyprland paints its "lockscreen app died" recovery screen, and every later idle-lock lands there again (lock-stranded: recovering is logged, but nothing recovers) until omarchy restart shell. Until then the session cannot be unlocked through the shell.
Why this is likely to bite more people now
This is exactly the shape of unattended, asynchronous agent work: a coding agent iterating on a shell plugin in the background while the user has stepped away and the idle lock has kicked in. Each plugin write reloads the shell under the lock, and the first one kills the lock screen. Here it was four aborts in a row (16:03–16:20), each immediately after a reload line; the user came back to a dead lock screen and a stack of Quickshell crash dialogs.
Repro
- Lock the session (idle lock, or
omarchy-shell lock lock). touch ~/.config/omarchy/plugins/<any enabled plugin>/manifest.json(or install a plugin).- Quickshell aborts and the lock UI disappears; the next idle-lock shows Hyprland's recovery screen instead.
Versions
Omarchy 3.8.5 (local checkout at ae7365f9 with one unrelated local patch), Quickshell 0.3.1 (Arch), Hyprland (a fork), kernel 7.1.9-arch1.
Suggestion
Defer plugin hot-reloads while the session is locked (queue them, apply on unlock), or reload everything except the lock surfaces. And let the lock-stranded: recovering path actually re-create the lock client instead of looping.
🤖 Generated with Claude Code
View raw text
**Filed by Claude (an AI agent, via Claude Code) at the direct request of @AndrewGaspar, whose machine hit this.**
## What happens
With the session locked by Omarchy's lock screen, any write under `~/.config/omarchy/plugins/` triggers the shell's plugin hot-reload (`Local plugin changed, reloading`), and Quickshell aborts:
FATAL: Tried to show lockscreen surfaces without active lock
After that the lock client is gone. Hyprland paints its "lockscreen app died" recovery screen, and every later idle-lock lands there again (`lock-stranded: recovering` is logged, but nothing recovers) until `omarchy restart shell`. Until then the session cannot be unlocked through the shell.
## Why this is likely to bite more people now
This is exactly the shape of unattended, asynchronous agent work: a coding agent iterating on a shell plugin in the background while the user has stepped away and the idle lock has kicked in. Each plugin write reloads the shell under the lock, and the first one kills the lock screen. Here it was four aborts in a row (16:03–16:20), each immediately after a reload line; the user came back to a dead lock screen and a stack of Quickshell crash dialogs.
## Repro
1. Lock the session (idle lock, or `omarchy-shell lock lock`).
2. `touch ~/.config/omarchy/plugins/<any enabled plugin>/manifest.json` (or install a plugin).
3. Quickshell aborts and the lock UI disappears; the next idle-lock shows Hyprland's recovery screen instead.
## Versions
Omarchy 3.8.5 (local checkout at ae7365f9 with one unrelated local patch), Quickshell 0.3.1 (Arch), Hyprland (a fork), kernel 7.1.9-arch1.
## Suggestion
Defer plugin hot-reloads while the session is locked (queue them, apply on unlock), or reload everything except the lock surfaces. And let the `lock-stranded: recovering` path actually re-create the lock client instead of looping.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
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.
No decision has been recorded yet.