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-763GitHub issuePublicDecided· Out of scope

CLI --help doesn't reveal sibling command with shared prefix (monitor internal vs monitor internal mirror)

Reported by vadimlungu · filed Sep 9, 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

CLI --help doesn't reveal sibling command with shared prefix (monitor internal vs monitor internal mirror)revision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

omarchy hyprland monitor internal --help prints only the usage for that one command:

Usage:
  omarchy hyprland monitor internal <on|off|toggle|recover>

Enable, disable, toggle, or recover the internal laptop display

It gives no indication that a separate, related sibling command exists:

omarchy hyprland monitor internal mirror <on|off|toggle|recover>

Because both routes share the internal prefix and both accept the exact same <on|off|toggle|recover> argument shape, running omarchy hyprland monitor internal toggle looks like it should toggle mirroring — but it actually toggles the laptop screen on/off, a completely different action. I ran it expecting to toggle mirror mode, saw no visible effect, and had no way to discover the correct command from --help alone.

The correct sibling command is listed, but only at the group level:

omarchy hyprland --help
omarchy hyprland monitor internal mirror <on|off|toggle|recover>  Enable, disable, toggle, or recover mirroring the internal display to an external monitor
omarchy hyprland monitor internal <on|off|toggle|recover>         Enable, disable, toggle, or recover the internal laptop display

What was expected

When two commands share a prefix (monitor internal and monitor internal mirror), running --help on the shorter one should mention the longer sibling command exists (e.g. an "also see" / "related commands" line), the way top-level command groups do.

Steps to reproduce

  1. omarchy hyprland monitor internal --help — shows only the on|off|toggle|recover usage for the internal-display toggle, no mention of mirror.
  2. Run omarchy hyprland monitor internal toggle expecting to toggle display mirroring — it silently does something else (toggles the laptop panel), not what a user asking for "mirror mode" wants.
  3. Compare with omarchy hyprland --help, which does list both commands side-by-side and disambiguates them.

System details

  • Omarchy version: 4.0.2-1

Suggested fix

When a command's --help output shares a name prefix with one or more sibling commands (e.g. monitor internal vs monitor internal mirror), append a short "related commands" note listing the sibling routes and their summaries.

View raw text
**What happened**

`omarchy hyprland monitor internal --help` prints only the usage for that one command:

```
Usage:
  omarchy hyprland monitor internal <on|off|toggle|recover>

Enable, disable, toggle, or recover the internal laptop display
```

It gives no indication that a separate, related sibling command exists:

```
omarchy hyprland monitor internal mirror <on|off|toggle|recover>
```

Because both routes share the `internal` prefix and both accept the exact same `<on|off|toggle|recover>` argument shape, running `omarchy hyprland monitor internal toggle` looks like it should toggle mirroring — but it actually toggles the laptop screen on/off, a completely different action. I ran it expecting to toggle mirror mode, saw no visible effect, and had no way to discover the correct command from `--help` alone.

The correct sibling command **is** listed, but only at the group level:

```
omarchy hyprland --help
```
```
omarchy hyprland monitor internal mirror <on|off|toggle|recover>  Enable, disable, toggle, or recover mirroring the internal display to an external monitor
omarchy hyprland monitor internal <on|off|toggle|recover>         Enable, disable, toggle, or recover the internal laptop display
```

**What was expected**

When two commands share a prefix (`monitor internal` and `monitor internal mirror`), running `--help` on the shorter one should mention the longer sibling command exists (e.g. an "also see" / "related commands" line), the way top-level command groups do.

**Steps to reproduce**

1. `omarchy hyprland monitor internal --help` — shows only the `on|off|toggle|recover` usage for the internal-display toggle, no mention of `mirror`.
2. Run `omarchy hyprland monitor internal toggle` expecting to toggle display mirroring — it silently does something else (toggles the laptop panel), not what a user asking for "mirror mode" wants.
3. Compare with `omarchy hyprland --help`, which does list both commands side-by-side and disambiguates them.

**System details**

- Omarchy version: 4.0.2-1

**Suggested fix**

When a command's `--help` output shares a name prefix with one or more sibling commands (e.g. `monitor internal` vs `monitor internal mirror`), append a short "related commands" note listing the sibling routes and their summaries.

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 11:20 UTC