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.
Add way to lock a config so Omarchy won't ever auto-update it
Reported by dhh · filed Aug 10, 2025Closed upstream on 2025-11-03 by its own reporter dhh, 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
We have folks doing a lot of careful customization to their Waybar and other Omarchy accessories. Right now all that is overwritten with omarchy-refresh-* when we need to update the defaults. A .bak file is then created, but you then have to manually merge things in. That feels grating. So how about this: We offer omarchy-lock waybar|walker|hypridle. That'll create ~/.local/state/omarchy/locks/waybar.config-lock. If that file exists, omarchy-refresh-waybar will NOT just overwrite. It'll perhaps just show the diff and offer to open the file so the user can manually merge in anything new?
That would still retain the Omarchy configs to evolve for people who enjoy the defaults, but also give folks the power to tinker as they see fit.
View raw text
We have folks doing a lot of careful customization to their Waybar and other Omarchy accessories. Right now all that is overwritten with omarchy-refresh-* when we need to update the defaults. A .bak file is then created, but you then have to manually merge things in. That feels grating. So how about this: We offer omarchy-lock waybar|walker|hypridle. That'll create ~/.local/state/omarchy/locks/waybar.config-lock. If that file exists, omarchy-refresh-waybar will NOT just overwrite. It'll perhaps just show the diff and offer to open the file so the user can manually merge in anything new? That would still retain the Omarchy configs to evolve for people who enjoy the defaults, but also give folks the power to tinker as they see fit.
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.