Proof Portal

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-5084GitHub issuePublicReceived

omarchy toggle bar on/off has inverted semantics

Reported by Starduster13 · filed Sep 14, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #7022 (R-1817). GitHub close reason: completed.

Open at source

Received and recorded verbatim. Nothing has been checked yet.

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

omarchy toggle bar on/off has inverted semanticsrevision 1 · captured 2026-10-04 12:10 UTC via poll

What happened

Running omarchy toggle bar on hides the top bar, and omarchy toggle bar off shows it — the opposite of what the command names say.

Expected behavior

omarchy toggle bar on should show the bar; omarchy toggle bar off should hide it.

Steps to reproduce

With the bar visible, run omarchy toggle bar on
Bar disappears
Run omarchy toggle bar off
Bar reappears

Root cause

omarchy-toggle-bar forwards the user's action straight through to the underlying flag without inverting it:

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

The state flag is named bar-off (its presence means the bar is hidden), but the wrapper passes on/off literally. So omarchy toggle bar on sets the bar-off flag on, which hides the bar, and omarchy toggle bar off clears it, showing the bar — inverted from the command's documented meaning (omarchy:examples=omarchy toggle bar | omarchy toggle bar off | omarchy toggle bar on).

A one-line fix would invert the passthrough, e.g.:

case "${1:-toggle}" in
  on) ACTION=off ;;
  off) ACTION=on ;;
  *) ACTION="${1:-toggle}" ;;
esac
omarchy-toggle bar-off "$ACTION"

(toggle needs no inversion since it just flips the current state either way.)

System details

Omarchy version: 4.0.3-1
Debug log: attached below (also see /tmp/omarchy-debug.log on the reporting system)

View raw text

## What happened

Running `omarchy toggle bar on` hides the top bar, and `omarchy toggle bar off` shows it — the opposite of what the command names say.

## Expected behavior

`omarchy toggle bar on` should show the bar; `omarchy toggle bar off` should hide it.

## Steps to reproduce

1. With the bar visible, run `omarchy toggle bar on`
2. Bar disappears
3. Run `omarchy toggle bar off`
4. Bar reappears

## Root cause

`omarchy-toggle-bar` forwards the user's action straight through to the underlying flag without inverting it:

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

The state flag is named `bar-off` (its *presence* means the bar is hidden), but the wrapper passes `on`/`off` literally. So `omarchy toggle bar on` sets the `bar-off` flag **on**, which hides the bar, and `omarchy toggle bar off` clears it, showing the bar — inverted from the command's documented meaning (`omarchy:examples=omarchy toggle bar | omarchy toggle bar off | omarchy toggle bar on`).

A one-line fix would invert the passthrough, e.g.:

```bash
case "${1:-toggle}" in
  on) ACTION=off ;;
  off) ACTION=on ;;
  *) ACTION="${1:-toggle}" ;;
esac
omarchy-toggle bar-off "$ACTION"
```

(`toggle` needs no inversion since it just flips the current state either way.)

## System details

- Omarchy version: 4.0.3-1
- Debug log: attached below (also see /tmp/omarchy-debug.log on the reporting system)

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.

Proof

History & reports

Reference