Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Bundled agent skills document 'omarchy debug', which is not a subcommand (should be 'omarchy-debug')
Reported by Taydevil · filed Sep 29, 2026 · open at source
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
System details
Intel Core i5-5257U, Intel Iris Graphics 6100 (Broadwell-U), MacBookPro12,1, Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy, Hyprland 0.56.2/Wayland
What's wrong?
Omarchy's own bundled agent skills instruct agents to run omarchy debug --no-sudo --print, but omarchy debug is not a valid subcommand. The real command is the standalone omarchy-debug binary. An agent following the shipped instructions literally hits exit 127 and has no diagnostic log.
This is agent-facing, so the blast radius is every Omarchy install that uses the bundled skills: the agent is handed a command that cannot work, at exactly the moment it needs diagnostics for a bug report.
Steps to reproduce
$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug
Run 'omarchy commands --all' to discover available commands.
$ echo $?
127
$ omarchy-debug --no-sudo --print | head -3
Date: Mon Sep 28 06:24:12 PM MDT 2026
Hostname: omarchy
Omarchy Package: omarchy 4.0.4-1
$ echo $?
0debug appears 0 times in omarchy commands --all. There is no omarchy debug subcommand in any form.
Wrong instructions shipped to agents
/usr/share/omarchy/default/agents/skills/omarchy/SKILL.md:
222: omarchy debug --no-sudo --print # Debug info (ALWAYS use these flags)
228: **IMPORTANT:** Always run `omarchy debug` with `--no-sudo --print` flags to avoid interactive sudo prompts that will hang the terminal.
234: omarchy debug --no-sudo --print/usr/share/omarchy/default/agents/skills/omarchy/contributing.md:
26: omarchy debug --no-sudo --print
28: # Interactive variant: `omarchy debug` offers to upload the log to logs.omarchy.org/usr/share/omarchy/default/agents/skills/diagnose-crash/reporting.md:
89: `omarchy version`, and diagnostics from `omarchy debug --no-sudo --print` (which
90: also writes `/tmp/omarchy-debug.log`; the interactive `omarchy debug` can uploadThe flags and the /tmp/omarchy-debug.log claim are both correct — only the command name is wrong. omarchy-debug --no-sudo --print exits 0 and does write /tmp/omarchy-debug.log (69KB).
Note
.github/ISSUE_TEMPLATE/bug.yml line 22 correctly says omarchy-debug, so the bug template and the bundled skills disagree. The template is right; the skills are wrong.
Expected
Either the skills use omarchy-debug, or a omarchy debug subcommand is added to dispatch to it. Since omarchy-debug is not a omarchy-* group command but a standalone binary, the skill text is the thing that needs fixing.
Impact
contributing.md and reporting.md are the guides an agent reads when it is asked to file an Omarchy bug. Following them produces a dead-end command, so the agent either files a report without diagnostics or stalls trying to produce them. It is a one-word fix repeated across three files.
View raw text
## System details Intel Core i5-5257U, Intel Iris Graphics 6100 (Broadwell-U), MacBookPro12,1, Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy, Hyprland 0.56.2/Wayland ## What's wrong? Omarchy's own bundled agent skills instruct agents to run `omarchy debug --no-sudo --print`, but `omarchy debug` is **not a valid subcommand**. The real command is the standalone `omarchy-debug` binary. An agent following the shipped instructions literally hits exit 127 and has no diagnostic log. This is agent-facing, so the blast radius is every Omarchy install that uses the bundled skills: the agent is handed a command that cannot work, at exactly the moment it needs diagnostics for a bug report. ### Steps to reproduce ```console $ omarchy debug --no-sudo --print Unknown Omarchy command: omarchy debug Run 'omarchy commands --all' to discover available commands. $ echo $? 127 $ omarchy-debug --no-sudo --print | head -3 Date: Mon Sep 28 06:24:12 PM MDT 2026 Hostname: omarchy Omarchy Package: omarchy 4.0.4-1 $ echo $? 0 ``` `debug` appears **0 times** in `omarchy commands --all`. There is no `omarchy debug` subcommand in any form. ### Wrong instructions shipped to agents `/usr/share/omarchy/default/agents/skills/omarchy/SKILL.md`: ``` 222: omarchy debug --no-sudo --print # Debug info (ALWAYS use these flags) 228: **IMPORTANT:** Always run `omarchy debug` with `--no-sudo --print` flags to avoid interactive sudo prompts that will hang the terminal. 234: omarchy debug --no-sudo --print ``` `/usr/share/omarchy/default/agents/skills/omarchy/contributing.md`: ``` 26: omarchy debug --no-sudo --print 28: # Interactive variant: `omarchy debug` offers to upload the log to logs.omarchy.org ``` `/usr/share/omarchy/default/agents/skills/diagnose-crash/reporting.md`: ``` 89: `omarchy version`, and diagnostics from `omarchy debug --no-sudo --print` (which 90: also writes `/tmp/omarchy-debug.log`; the interactive `omarchy debug` can upload ``` The flags and the `/tmp/omarchy-debug.log` claim are both correct — only the command name is wrong. `omarchy-debug --no-sudo --print` exits 0 and does write `/tmp/omarchy-debug.log` (69KB). ### Note `.github/ISSUE_TEMPLATE/bug.yml` line 22 correctly says `omarchy-debug`, so the bug template and the bundled skills disagree. The template is right; the skills are wrong. ### Expected Either the skills use `omarchy-debug`, or a `omarchy debug` subcommand is added to dispatch to it. Since `omarchy-debug` is not a `omarchy-*` group command but a standalone binary, the skill text is the thing that needs fixing. ### Impact `contributing.md` and `reporting.md` are the guides an agent reads when it is asked to file an Omarchy bug. Following them produces a dead-end command, so the agent either files a report without diagnostics or stalls trying to produce them. It is a one-word fix repeated across three files.
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 20:06 UTC