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 on/off arguments are inverted — 'on' hides the bar
Reported by brendanhalfpenny · filed Aug 31, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #7022 (R-1817). GitHub close reason: completed.
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 bar, and omarchy toggle bar off shows it — the opposite of what the words say.
Cause
omarchy-toggle-bar passes the user's on|off argument straight through to the underlying flag, which is named for the inverse state:
omarchy-toggle bar-off "${1:-toggle}"So "bar on" sets the bar-off flag (bar hidden), and "bar off" clears it (bar shown). The bare toggle form behaves fine; only the explicit on/off arguments are inverted.
Expected
omarchy toggle bar on → bar visible; omarchy toggle bar off → bar hidden. The wrapper should invert the argument before passing it to the bar-off flag (or the flag could be renamed).
System details
Omarchy 4.0.1-1
(Noticed while recovering a stuck-hidden bar: separately, the bar can remain hidden after a fullscreen window closes, with no bar-off flag set — mentioning in case it's related, but the inverted argument is the concrete reproducible bug here.)
View raw text
## What happened
`omarchy toggle bar on` **hides** the bar, and `omarchy toggle bar off` shows it — the opposite of what the words say.
## Cause
`omarchy-toggle-bar` passes the user's `on|off` argument straight through to the underlying flag, which is named for the inverse state:
```bash
omarchy-toggle bar-off "${1:-toggle}"
```
So "bar **on**" sets the `bar-off` flag (bar hidden), and "bar **off**" clears it (bar shown). The bare `toggle` form behaves fine; only the explicit `on`/`off` arguments are inverted.
## Expected
`omarchy toggle bar on` → bar visible; `omarchy toggle bar off` → bar hidden. The wrapper should invert the argument before passing it to the `bar-off` flag (or the flag could be renamed).
## System details
Omarchy 4.0.1-1
(Noticed while recovering a stuck-hidden bar: separately, the bar can remain hidden after a fullscreen window closes, with no `bar-off` flag set — mentioning in case it's related, but the inverted argument is the concrete reproducible bug here.)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.