Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1817GitHub issuePublicFixed

omarchy toggle bar on/off has inverted semantics (hides bar on 'on', shows it on 'off')

Reported by Amvurguezo · filed Aug 15, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

omarchy toggle bar on/off has inverted semantics (hides bar on 'on', shows it on 'off')revision 1 · captured 2026-09-28 21:29 UTC via poll

What happened

Running omarchy toggle bar on hides the top bar, and omarchy toggle bar off shows it — the exact opposite of what the command name and its own documented examples imply.

Root cause: omarchy-toggle-bar forwards the raw on/off argument straight through to the underlying bar-off flag without inverting it:

$ cat $(which omarchy-toggle-bar)
#!/bin/bash

# omarchy:summary=Toggle bar visibility without killing the Omarchy shell
# omarchy:args=[toggle|on|off]
# omarchy:examples=omarchy toggle bar | omarchy toggle bar off | omarchy toggle bar on

omarchy-toggle bar-off "${1:-toggle}"

Since the underlying flag is named bar-off (true = bar is hidden), passing on sets bar-off to enabled (bar hidden), and passing off disables bar-off (bar shown). The wrapper needs to invert the action before forwarding it to the bar-off flag, e.g. map on -> off and off -> on (and leave toggle as-is).

How I found it / reproduction

  1. On a fresh boot the top bar wasn't rendering at all, even though the omarchy-shell (quickshell) process was alive.
  2. hyprctl layers showed the omarchy-bar layer surface existing but positioned off-screen: xywh: 1920 -26 1920 26 (26px above the visible monitor area, i.e. in its hidden position).
  3. omarchy toggle enabled bar-off returned exit code 0, confirming the bar-off flag was active (bar hidden).
  4. Ran omarchy toggle bar on expecting it to show the bar — instead omarchy toggle enabled bar-off still returned 0 (still hidden), and the layer stayed at y: -26.
  5. Ran omarchy toggle bar off instead — the bar-off flag was cleared (omarchy toggle enabled bar-off now returns exit 1), and hyprctl layers immediately showed the bar back at xywh: 1920 0 1920 26 (visible).

So functionally:
- omarchy toggle bar on → bar hidden
- omarchy toggle bar off → bar shown

Expected

  • omarchy toggle bar on → bar visible
  • omarchy toggle bar off → bar hidden

matching the command's own summary/examples ("Toggle bar visibility... omarchy toggle bar off | omarchy toggle bar on").

System details

  • Omarchy version: 4.0.0-1
  • Compositor: Hyprland (single laptop panel monitor, eDP-1, active at the time of testing)
  • omarchy debug is not an available command on this version (omarchy commands --all has no debug entry), so I couldn't attach the standard diagnostic log.

Suggested fix

In omarchy-toggle-bar (or wherever it lives in the source tree), invert the action before forwarding to the bar-off flag, e.g.:

#!/bin/bash
case "${1:-toggle}" in
  on) omarchy-toggle bar-off off ;;
  off) omarchy-toggle bar-off on ;;
  *) omarchy-toggle bar-off toggle ;;
esac

Happy to open a PR with this fix if useful.

View raw text
## What happened

Running `omarchy toggle bar on` **hides** the top bar, and `omarchy toggle bar off` **shows** it — the exact opposite of what the command name and its own documented examples imply.

Root cause: `omarchy-toggle-bar` forwards the raw `on`/`off` argument straight through to the underlying `bar-off` flag without inverting it:

```bash
$ cat $(which omarchy-toggle-bar)
#!/bin/bash

# omarchy:summary=Toggle bar visibility without killing the Omarchy shell
# omarchy:args=[toggle|on|off]
# omarchy:examples=omarchy toggle bar | omarchy toggle bar off | omarchy toggle bar on

omarchy-toggle bar-off "${1:-toggle}"
```

Since the underlying flag is named `bar-off` (true = bar is hidden), passing `on` sets `bar-off` to enabled (bar hidden), and passing `off` disables `bar-off` (bar shown). The wrapper needs to invert the action before forwarding it to the `bar-off` flag, e.g. map `on -> off` and `off -> on` (and leave `toggle` as-is).

## How I found it / reproduction

1. On a fresh boot the top bar wasn't rendering at all, even though the `omarchy-shell` (quickshell) process was alive.
2. `hyprctl layers` showed the `omarchy-bar` layer surface existing but positioned off-screen: `xywh: 1920 -26 1920 26` (26px above the visible monitor area, i.e. in its hidden position).
3. `omarchy toggle enabled bar-off` returned exit code `0`, confirming the `bar-off` flag was active (bar hidden).
4. Ran `omarchy toggle bar on` expecting it to show the bar — instead `omarchy toggle enabled bar-off` still returned `0` (still hidden), and the layer stayed at `y: -26`.
5. Ran `omarchy toggle bar off` instead — the `bar-off` flag was cleared (`omarchy toggle enabled bar-off` now returns exit `1`), and `hyprctl layers` immediately showed the bar back at `xywh: 1920 0 1920 26` (visible).

So functionally:
- `omarchy toggle bar on` → bar hidden
- `omarchy toggle bar off` → bar shown

## Expected

- `omarchy toggle bar on` → bar visible
- `omarchy toggle bar off` → bar hidden

matching the command's own summary/examples ("Toggle bar visibility... omarchy toggle bar off | omarchy toggle bar on").

## System details

- Omarchy version: `4.0.0-1`
- Compositor: Hyprland (single laptop panel monitor, `eDP-1`, active at the time of testing)
- `omarchy debug` is not an available command on this version (`omarchy commands --all` has no `debug` entry), so I couldn't attach the standard diagnostic log.

## Suggested fix

In `omarchy-toggle-bar` (or wherever it lives in the source tree), invert the action before forwarding to the `bar-off` flag, e.g.:

```bash
#!/bin/bash
case "${1:-toggle}" in
  on) omarchy-toggle bar-off off ;;
  off) omarchy-toggle bar-off on ;;
  *) omarchy-toggle bar-off toggle ;;
esac
```

Happy to open a PR with this fix if useful.

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

  • Fixed bypr/12155· confirmed

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 04:13 UTC