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.
Confirm destructive power actions in the system menu
Reported by ferlemes · filed Sep 2, 2026 · open at source
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?
- 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. So far: in the audited area (menu) — decided by agents · verified; matches no known issue — decided by agents · verified; not a duplicate of another report — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.
Original report
Problem
The System menu executes Reboot and Shutdown immediately after activation. Because these actions sit next to other frequently used session actions, an accidental click or key press can interrupt work without a chance to recover.
This is especially surprising in a keyboard-driven launcher, where a stray Enter can turn a navigation mistake into a destructive system action.
Suggested behavior
Require a short, keyboard-friendly confirmation for Reboot and Shutdown when they are launched from the Omarchy menu:
- show a native shell confirmation dialog;
- select Cancel by default;
- allow Escape to cancel and arrows/Tab to change the selection;
- show a five-second countdown on the destructive action;
- execute automatically when the countdown reaches zero.
Direct calls to omarchy system reboot and omarchy system shutdown should remain immediate. This keeps scripts, terminal workflows, and internal Omarchy calls unchanged while protecting the interactive menu path.
Why a native dialog
A shell-native dialog is consistent with the rest of the menu, keeps focus and keyboard navigation predictable, and avoids launching a temporary terminal solely for confirmation.
I have a working implementation with focused menu tests and will open a PR linked to this issue.
View raw text
## Problem The System menu executes Reboot and Shutdown immediately after activation. Because these actions sit next to other frequently used session actions, an accidental click or key press can interrupt work without a chance to recover. This is especially surprising in a keyboard-driven launcher, where a stray Enter can turn a navigation mistake into a destructive system action. ## Suggested behavior Require a short, keyboard-friendly confirmation for Reboot and Shutdown when they are launched from the Omarchy menu: - show a native shell confirmation dialog; - select Cancel by default; - allow Escape to cancel and arrows/Tab to change the selection; - show a five-second countdown on the destructive action; - execute automatically when the countdown reaches zero. Direct calls to `omarchy system reboot` and `omarchy system shutdown` should remain immediate. This keeps scripts, terminal workflows, and internal Omarchy calls unchanged while protecting the interactive menu path. ## Why a native dialog A shell-native dialog is consistent with the rest of the menu, keeps focus and keyboard navigation predictable, and avoids launching a temporary terminal solely for confirmation. I have a working implementation with focused menu tests and will open a PR linked to this issue.
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
- Fixed bypr/9838· 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.
- Decided by agents · verified: in the audited area (menu)
- Decided by agents · verified: matches no known issue
- Decided by agents · verified: not a duplicate of another report
The outcome (valid, duplicate, not a bug, …) is not decided yet.