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.
Rename config refresh commands to reset
Reported by shbernal · filed May 29, 2026Closed upstream on 2026-07-18. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not 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
Problem
Omarchy currently uses refresh for commands that reset user configs back to Omarchy defaults, for example:
omarchy refresh waybaromarchy refresh hyprlandomarchy refresh config <file>- legacy command names like
omarchy-refresh-waybarandomarchy-refresh-config
That wording is confusing because refresh usually suggests reloading, updating, or applying the latest config without destructive changes. The actual behavior is a reset: current user config is backed up, then replaced with the Omarchy default.
I would expect the word to be reset, not refresh.
Why this matters
The current wording makes destructive operations sound safer than they are. This has shown up around related config-reset behavior in issues such as:
- #5821, where
omarchy refresh waybaroverwrites user Waybar customizations - #5764, where a Waybar position command reset custom config and style
- #2507, where
omarchy-refresh-hyprlandreset keyboard layout-related config
Those issues are about behavior and preservation. This issue is specifically about the command/menu vocabulary.
Suggested change
Introduce reset wording for config-default operations, for example:
omarchy reset waybaromarchy reset hyprlandomarchy reset config <file>
Keep refresh aliases for backward compatibility if needed, but show reset in menus, help text, docs, and examples.
Expected result
Users can tell from the command name that the operation restores defaults and overwrites current config, even though a backup is created.
View raw text
## Problem Omarchy currently uses `refresh` for commands that reset user configs back to Omarchy defaults, for example: - `omarchy refresh waybar` - `omarchy refresh hyprland` - `omarchy refresh config <file>` - legacy command names like `omarchy-refresh-waybar` and `omarchy-refresh-config` That wording is confusing because `refresh` usually suggests reloading, updating, or applying the latest config without destructive changes. The actual behavior is a reset: current user config is backed up, then replaced with the Omarchy default. I would expect the word to be `reset`, not `refresh`. ## Why this matters The current wording makes destructive operations sound safer than they are. This has shown up around related config-reset behavior in issues such as: - #5821, where `omarchy refresh waybar` overwrites user Waybar customizations - #5764, where a Waybar position command reset custom config and style - #2507, where `omarchy-refresh-hyprland` reset keyboard layout-related config Those issues are about behavior and preservation. This issue is specifically about the command/menu vocabulary. ## Suggested change Introduce `reset` wording for config-default operations, for example: - `omarchy reset waybar` - `omarchy reset hyprland` - `omarchy reset config <file>` Keep `refresh` aliases for backward compatibility if needed, but show `reset` in menus, help text, docs, and examples. ## Expected result Users can tell from the command name that the operation restores defaults and overwrites current config, even though a backup is created.
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.