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.
Agent skills instruct an "ALWAYS" diagnostic step that does not exist (`omarchy debug`), and name the old basecamp/omarchy repo
Reported by leonrlr4 · filed Sep 12, 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
What happened
default/agents/skills/ ships two skills whose text an agent follows literally. Two of those instructions are wrong on 4.0.3.
1. `omarchy debug` does not exist, but the skill says to always use it.
default/agents/skills/omarchy/SKILL.md:
- line 222 —
omarchy debug --no-sudo --print # Debug info (ALWAYS use these flags) - line 228 — "IMPORTANT: Always run
omarchy debugwith--no-sudo --printflags to avoid interactive sudo prompts that will hang the terminal." - line 234 — the same command again, under Troubleshooting
On 4.0.3-1 every entry point fails:
$ omarchy debug
Unknown Omarchy command: omarchy debug
$ omarchy debug --help
Unknown Omarchy command: omarchy debug --help
$ omarchy commands --all | grep -c '^ *omarchy debug'
0What makes this convincing rather than obviously stale is that omarchy --help advertises the command in two places:
Common commands:
omarchy debug Print debugging information
Groups:
debug Diagnostics and support logsSo the help output says it exists, the skill says to always run it, and nothing dispatches it. An agent that follows the skill collects no diagnostics and gets no signal that the step failed — it just sees "Unknown Omarchy command" and has been told this is the supported way.
default/agents/skills/diagnose-crash/reporting.md lines 89-91 build the upstream bug-report step on the same command, including a /tmp/omarchy-debug.log path and an interactive upload flow that returns a shareable URL.
2. The repo name is stale.
diagnose-crash/reporting.md lines 43, 44, 62, 77 and 85, plus omarchy/contributing.md line 6, all say basecamp/omarchy. The canonical repo is omacom/omarchy. gh follows the redirect so the commands still work, but an agent writing a report quotes the wrong name.
Expected
Either dispatch omarchy debug, or drop it from omarchy --help and replace the skill instruction with commands that exist, for example:
omarchy version
hyprctl version
pacman -Q quickshell hyprland
journalctl -b -t omarchy-shell --no-pager | tail -50
hyprctl configerrorsand update the two files that still name basecamp/omarchy.
Versions
omarchy 4.0.3-1; both skill files are owned by omarchy-settings 4.0.3-1.
View raw text
### What happened `default/agents/skills/` ships two skills whose text an agent follows literally. Two of those instructions are wrong on 4.0.3. **1. `omarchy debug` does not exist, but the skill says to always use it.** `default/agents/skills/omarchy/SKILL.md`: - line 222 — `omarchy debug --no-sudo --print # Debug info (ALWAYS use these flags)` - line 228 — "**IMPORTANT:** Always run `omarchy debug` with `--no-sudo --print` flags to avoid interactive sudo prompts that will hang the terminal." - line 234 — the same command again, under Troubleshooting On 4.0.3-1 every entry point fails: ``` $ omarchy debug Unknown Omarchy command: omarchy debug $ omarchy debug --help Unknown Omarchy command: omarchy debug --help $ omarchy commands --all | grep -c '^ *omarchy debug' 0 ``` What makes this convincing rather than obviously stale is that `omarchy --help` advertises the command in two places: ``` Common commands: omarchy debug Print debugging information Groups: debug Diagnostics and support logs ``` So the help output says it exists, the skill says to always run it, and nothing dispatches it. An agent that follows the skill collects no diagnostics and gets no signal that the step failed — it just sees "Unknown Omarchy command" and has been told this is the supported way. `default/agents/skills/diagnose-crash/reporting.md` lines 89-91 build the upstream bug-report step on the same command, including a `/tmp/omarchy-debug.log` path and an interactive upload flow that returns a shareable URL. **2. The repo name is stale.** `diagnose-crash/reporting.md` lines 43, 44, 62, 77 and 85, plus `omarchy/contributing.md` line 6, all say `basecamp/omarchy`. The canonical repo is `omacom/omarchy`. `gh` follows the redirect so the commands still work, but an agent writing a report quotes the wrong name. ### Expected Either dispatch `omarchy debug`, or drop it from `omarchy --help` and replace the skill instruction with commands that exist, for example: ```bash omarchy version hyprctl version pacman -Q quickshell hyprland journalctl -b -t omarchy-shell --no-pager | tail -50 hyprctl configerrors ``` and update the two files that still name `basecamp/omarchy`. ### Versions omarchy 4.0.3-1; both skill files are owned by `omarchy-settings 4.0.3-1`.
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 12:06 UTC