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 toggle bar has inverted on/off semantics — on hides the bar, off shows it
Reported by derekbeins · filed Aug 29, 2026Closed upstream on 2026-09-04 by spencerbull, as a duplicate of #7022 (R-1817). GitHub close reason: duplicate.
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
What happened
omarchy toggle bar on hides the top bar. omarchy toggle bar off shows it. This is backwards from every other omarchy toggle <feature> [on|off] command, where on enables/shows and off disables/hides.
Expected
omarchy toggle bar on shows the bar; omarchy toggle bar off hides it.
Root cause
/usr/share/omarchy/bin/omarchy-toggle-bar:
omarchy-toggle bar-off "${1:-toggle}"The underlying flag is named bar-off (state file ~/.local/state/omarchy/toggles/bar-off), and omarchy-toggle's generic on/off handling just creates or removes that flag file directly — on creates bar-off (hides the bar), off removes it (shows the bar). The wrapper forwards the user's on/off argument straight through to the bar-off flag without inverting it, so the sense of the flag leaks into the CLI's public argument semantics.
Steps to reproduce
omarchy toggle bar off(bar is now visible, if it wasn't already)omarchy toggle bar on— bar disappearshyprctl layersshows theomarchy-barlayer still present but shifted fully off-screen (y = -<bar height>), confirming it's a visibility-flag issue, not a crash
System details
- Omarchy 4.0.1-1
- Hyprland/Wayland
- MacBookPro11,3 (Intel Iris Pro 5200 driving the internal panel via GPU mux)
- Kernel 7.1.9-arch1-2
Fix suggestion
Invert the argument in omarchy-toggle-bar before forwarding to the generic toggle, e.g. map on→off and off→on for the bar-off flag, or rename the flag semantics so on/off map directly.
View raw text
### What happened
`omarchy toggle bar on` hides the top bar. `omarchy toggle bar off` shows it. This is backwards from every other `omarchy toggle <feature> [on|off]` command, where `on` enables/shows and `off` disables/hides.
### Expected
`omarchy toggle bar on` shows the bar; `omarchy toggle bar off` hides it.
### Root cause
`/usr/share/omarchy/bin/omarchy-toggle-bar`:
```
omarchy-toggle bar-off "${1:-toggle}"
```
The underlying flag is named `bar-off` (state file `~/.local/state/omarchy/toggles/bar-off`), and `omarchy-toggle`'s generic `on`/`off` handling just creates or removes that flag file directly — `on` creates `bar-off` (hides the bar), `off` removes it (shows the bar). The wrapper forwards the user's `on`/`off` argument straight through to the `bar-off` flag without inverting it, so the sense of the flag leaks into the CLI's public argument semantics.
### Steps to reproduce
1. `omarchy toggle bar off` (bar is now visible, if it wasn't already)
2. `omarchy toggle bar on` — bar disappears
3. `hyprctl layers` shows the `omarchy-bar` layer still present but shifted fully off-screen (y = -<bar height>), confirming it's a visibility-flag issue, not a crash
### System details
- Omarchy 4.0.1-1
- Hyprland/Wayland
- MacBookPro11,3 (Intel Iris Pro 5200 driving the internal panel via GPU mux)
- Kernel 7.1.9-arch1-2
### Fix suggestion
Invert the argument in `omarchy-toggle-bar` before forwarding to the generic toggle, e.g. map `on`→`off` and `off`→`on` for the `bar-off` flag, or rename the flag semantics so `on`/`off` map directly.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.