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.
omarchy refresh waybar overwrites user customizations without warning
Reported by Esegnorelli · filed May 14, 2026Closed upstream on 2026-05-15 by dhh. 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 refresh waybar calls omarchy-refresh-config on both waybar/config.jsonc and waybar/style.css, which replaces the files wholesale with Omarchy defaults. Any user customizations to modules, layout, or styles are silently lost (only a timestamped .bak file is kept).
The script currently preserves only three layout properties (position, height, width) via sed post-processing, but any other user changes — for example custom modules, additional CSS rules, or modified module configs — are wiped.
Steps to reproduce
- Add custom modules or CSS to
~/.config/waybar/config.jsoncorstyle.css - Run
omarchy refresh waybar - All customizations are gone; only
position,height, andwidthsurvive
Suggested improvement
Rather than replacing the full files, omarchy refresh waybar could:
- Document clearly that it is a destructive reset (the current summary "Reset Waybar config to Omarchy defaults" is accurate but easy to overlook), and/or
- Prompt for confirmation before overwriting if the user config differs from the default, or
- Support a user overlay/include pattern (e.g. a
~/.config/waybar/user.jsoncmerged at the end, or a CSS@importfor user styles) so customizations survive a refresh
Context
Discovered after an Omarchy migration switched the workspace display from hyprland/workspaces to custom custom/ws* modules. Running omarchy refresh waybar as part of troubleshooting silently reverted all those changes.
View raw text
## Problem `omarchy refresh waybar` calls `omarchy-refresh-config` on both `waybar/config.jsonc` and `waybar/style.css`, which replaces the files wholesale with Omarchy defaults. Any user customizations to modules, layout, or styles are silently lost (only a timestamped `.bak` file is kept). The script currently preserves only three layout properties (`position`, `height`, `width`) via `sed` post-processing, but any other user changes — for example custom modules, additional CSS rules, or modified module configs — are wiped. ## Steps to reproduce 1. Add custom modules or CSS to `~/.config/waybar/config.jsonc` or `style.css` 2. Run `omarchy refresh waybar` 3. All customizations are gone; only `position`, `height`, and `width` survive ## Suggested improvement Rather than replacing the full files, `omarchy refresh waybar` could: - **Document clearly** that it is a destructive reset (the current summary "Reset Waybar config to Omarchy defaults" is accurate but easy to overlook), and/or - **Prompt for confirmation** before overwriting if the user config differs from the default, or - **Support a user overlay/include** pattern (e.g. a `~/.config/waybar/user.jsonc` merged at the end, or a CSS `@import` for user styles) so customizations survive a refresh ## Context Discovered after an Omarchy migration switched the workspace display from `hyprland/workspaces` to custom `custom/ws*` modules. Running `omarchy refresh waybar` as part of troubleshooting silently reverted all those changes.
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.