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

omarchy toggle bar on/off is inverted

Reported by stephenlenton · filed Sep 14, 2026Closed upstream on 2026-09-14 by its own reporter stephenlenton, as not planned. Closed by its own reporter — not by itself evidence of a fix.

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 is invertedrevision 1 · captured 2026-10-04 12:10 UTC via poll

What happened

omarchy toggle bar on and omarchy toggle bar off do the opposite of what
their names say. Running omarchy toggle bar on hides the top bar, and
omarchy toggle bar off is what actually shows it again.

Why

/usr/share/omarchy/bin/omarchy-toggle-bar forwards its argument straight
through to the generic flag toggler, against a flag file literally named
bar-off:

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

omarchy-toggle's on action enables (creates) the named flag file, and
off disables (removes) it:

case "$ACTION" in
  ...
  on)
    enable
    ;;
  off)
    disable
    ;;

So omarchy toggle bar on creates ~/.local/state/omarchy/toggles/bar-off
(bar-off = enabled → bar hidden), and omarchy toggle bar off removes it
(bar-off = disabled → bar shown). The polarity needs to be inverted in
omarchy-toggle-bar, e.g. mapping on→disable bar-off and off→`enable
bar-off` before (or instead of) calling the generic toggle.

The bare omarchy toggle bar (no argument) is unaffected, since plain
toggling doesn't care about the flag's semantic name.

Steps to reproduce

Confirm the bar is currently visible.
Run omarchy toggle bar on.
Observe the bar disappears (its layer surface parks itself just off-screen

— hyprctl layers shows it shifted by exactly its own height past the
monitor edge, e.g. y: 2414 against a monitor top at y: 2440 for a
26px-tall bar).
4. Run omarchy toggle bar off.
5. Observe the bar reappears.

Expected behavior

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

System details

Omarchy version: 4.0.3-1
Hyprland: 0.56.2 (v0.56.2, commit efb5099)
Kernel: 7.2.3-arch1-3
Note: omarchy debug is not a recognized command on this Omarchy version

(omarchy commands --all lists no debug command), so no diagnostic log
URL is attached.

View raw text

## What happened

`omarchy toggle bar on` and `omarchy toggle bar off` do the opposite of what
their names say. Running `omarchy toggle bar on` hides the top bar, and
`omarchy toggle bar off` is what actually shows it again.

## Why

`/usr/share/omarchy/bin/omarchy-toggle-bar` forwards its argument straight
through to the generic flag toggler, against a flag file literally named
`bar-off`:

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

`omarchy-toggle`'s `on` action *enables* (creates) the named flag file, and
`off` *disables* (removes) it:

```bash
case "$ACTION" in
  ...
  on)
    enable
    ;;
  off)
    disable
    ;;
```

So `omarchy toggle bar on` creates `~/.local/state/omarchy/toggles/bar-off`
(bar-off = enabled → bar hidden), and `omarchy toggle bar off` removes it
(bar-off = disabled → bar shown). The polarity needs to be inverted in
`omarchy-toggle-bar`, e.g. mapping `on`→`disable bar-off` and `off`→`enable
bar-off` before (or instead of) calling the generic toggle.

The bare `omarchy toggle bar` (no argument) is unaffected, since plain
toggling doesn't care about the flag's semantic name.

## Steps to reproduce

1. Confirm the bar is currently visible.
2. Run `omarchy toggle bar on`.
3. Observe the bar disappears (its layer surface parks itself just off-screen
   — `hyprctl layers` shows it shifted by exactly its own height past the
   monitor edge, e.g. `y: 2414` against a monitor top at `y: 2440` for a
   26px-tall bar).
4. Run `omarchy toggle bar off`.
5. Observe the bar reappears.

## Expected behavior

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

## System details

- Omarchy version: 4.0.3-1
- Hyprland: 0.56.2 (v0.56.2, commit efb5099)
- Kernel: 7.2.3-arch1-3
- Note: `omarchy debug` is not a recognized command on this Omarchy version
  (`omarchy commands --all` lists no `debug` command), so no diagnostic log
  URL is attached.

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