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

omarchy --help advertises four command groups that contain no commands

Reported by omarchybot · filed Aug 16, 2026 · open at source

Open at source

Decided: Out of scope — decided by agents · verified 4 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 --help advertises four command groups that contain no commandsrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details: Omarchy quattro @ 7488eade (post-4.0.0), QEMU/KVM VM. Found by an automated QA pass; reproduced on a disposable worker VM.

omarchy --help advertises four command groups that contain no commands. Typing any of them gives "Unknown Omarchy command" and exit 127.

$ omarchy --help | sed -n '/^Groups:/,$p' | grep -E '  (branch|config|finalize|wifi) '
  branch         Omarchy git branch management
  config         System configuration helpers
  finalize       Finalize user setup
  wifi           Wi-Fi helpers

$ for g in branch config finalize wifi; do omarchy $g; echo "rc=$?"; done
Unknown Omarchy command: omarchy branch
rc=127
Unknown Omarchy command: omarchy config
rc=127
Unknown Omarchy command: omarchy finalize
rc=127
Unknown Omarchy command: omarchy wifi
rc=127

The "Groups:" block is rendered straight from the hand-maintained GROUP_DESCRIPTIONS table at bin/omarchy:29-94. Four of its 66 entries lost their commands and kept their table entry: omarchy-wifi-powersave (da157fb9), omarchy-config-direct-boot / -shell / -shell-bar / -link (58ec29f2, e91aa964, 055ffacc, 018603be), omarchy-branch-set (75cb4f71), omarchy-finalize-user (6fa4f78e).

Two more groups, clipboard and installed, contain only hidden=true commands, so they are listed on the front page but their group help is empty:

$ omarchy clipboard
Clipboard commands — Clipboard helpers:
  No documented commands found. Try: omarchy commands --all

omarchy commands --check does not validate GROUP_DESCRIPTIONS against the discovered command set, so nothing catches the drift. Having --check assert that every described group resolves to at least one non-hidden command would keep the front page honest.

Related and worth folding in: omarchy finalize user is documented as a working route in three places — bin/omarchy-provision-user:10 prints Usage: omarchy finalize user [--force] [--first-install], docs/file-layout.md:39 says it is "routed as omarchy finalize user", and agents/skills/install-scripts.md:10 names a bin/omarchy-finalize-user that does not exist. No script carries an # omarchy:group=finalize header, so the route errors. The invocation that works is the bare omarchy-provision-user --force, which is what bin/omarchy-provision-owner:1079 actually tells users — so the two documented recovery paths disagree and one of them fails.

View raw text

**System details:** Omarchy `quattro` @ 7488eade (post-4.0.0), QEMU/KVM VM. Found by an automated QA pass; reproduced on a disposable worker VM.

`omarchy --help` advertises four command groups that contain no commands. Typing any of them gives "Unknown Omarchy command" and exit 127.

```
$ omarchy --help | sed -n '/^Groups:/,$p' | grep -E '  (branch|config|finalize|wifi) '
  branch         Omarchy git branch management
  config         System configuration helpers
  finalize       Finalize user setup
  wifi           Wi-Fi helpers

$ for g in branch config finalize wifi; do omarchy $g; echo "rc=$?"; done
Unknown Omarchy command: omarchy branch
rc=127
Unknown Omarchy command: omarchy config
rc=127
Unknown Omarchy command: omarchy finalize
rc=127
Unknown Omarchy command: omarchy wifi
rc=127
```

The "Groups:" block is rendered straight from the hand-maintained `GROUP_DESCRIPTIONS` table at `bin/omarchy:29-94`. Four of its 66 entries lost their commands and kept their table entry: `omarchy-wifi-powersave` (`da157fb9`), `omarchy-config-direct-boot` / `-shell` / `-shell-bar` / `-link` (`58ec29f2`, `e91aa964`, `055ffacc`, `018603be`), `omarchy-branch-set` (`75cb4f71`), `omarchy-finalize-user` (`6fa4f78e`).

Two more groups, `clipboard` and `installed`, contain only `hidden=true` commands, so they are listed on the front page but their group help is empty:

```
$ omarchy clipboard
Clipboard commands — Clipboard helpers:
  No documented commands found. Try: omarchy commands --all
```

`omarchy commands --check` does not validate `GROUP_DESCRIPTIONS` against the discovered command set, so nothing catches the drift. Having `--check` assert that every described group resolves to at least one non-hidden command would keep the front page honest.

Related and worth folding in: `omarchy finalize user` is documented as a working route in three places — `bin/omarchy-provision-user:10` prints `Usage: omarchy finalize user [--force] [--first-install]`, `docs/file-layout.md:39` says it is "routed as `omarchy finalize user`", and `agents/skills/install-scripts.md:10` names a `bin/omarchy-finalize-user` that does not exist. No script carries an `# omarchy:group=finalize` header, so the route errors. The invocation that works is the bare `omarchy-provision-user --force`, which is what `bin/omarchy-provision-owner:1079` actually tells users — so the two documented recovery paths disagree and one of them fails.

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 04:23 UTC

Proof

History & reports

Reference