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

omarchy skill documents 'omarchy debug', which does not exist (use omarchy-debug)

Reported by FizzyCustard · filed Sep 20, 2026Closed upstream on 2026-10-12 by the bot omarchybot, as a duplicate (target not recorded).

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

omarchy skill documents 'omarchy debug', which does not exist (use omarchy-debug)revision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

The bundled omarchy agent skill instructs AI agents to gather diagnostics with:

omarchy debug --no-sudo --print

That command does not exist in Omarchy 4.0.4-1:

$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print
Run 'omarchy commands --all' to discover available commands.

omarchy commands --all lists no debug route.

What I expected

Either the documented command to work, or the skill to reference the form that
does.

The binary exists — it just isn't routed

/usr/bin/omarchy-debug is present and works correctly with the same flags:

$ omarchy-debug --no-sudo --print
Date: Sun Sep 20 12:45:41 PM BST 2026
Hostname: omarchy
Omarchy Package: omarchy 4.0.4-1
...

So this looks like the skill documenting a dispatcher route (omarchy <group>)
that was never wired up for this binary, rather than a missing feature.

Affected files

In /usr/share/omarchy/default/agents/skills/omarchy/:

File	Lines
`SKILL.md`	222, 228, 234
`contributing.md`	26, 28

SKILL.md:228 also states **"Always run omarchy debug with `--no-sudo
--print` flags"**, reinforcing the non-working form.

Why it matters

The skill is symlinked into ~/.claude/skills/omarchy, so agents follow it as
authoritative. It is also read-only and root-owned, and the skill correctly warns
against editing /usr/share/omarchy/, so users cannot patch it locally without
having their change wiped by the next omarchy update.

The sharpest edge is that contributing.md is specifically the bug reporting
guide — so the failure lands exactly when an agent is trying to collect
diagnostics for an Omarchy issue. I hit this while gathering details for #12628
and had to assemble the system information by hand.

Suggested fix

Replace omarchy debug with omarchy-debug in the five places above, or add a
debug route to the dispatcher so the documented form works.

System details


Omarchy	4.0.4-1 (stable channel)
Machine	Apple Macmini7,1

View raw text

## What happened

The bundled `omarchy` agent skill instructs AI agents to gather diagnostics with:

```bash
omarchy debug --no-sudo --print
```

That command does not exist in Omarchy 4.0.4-1:

```
$ omarchy debug --no-sudo --print
Unknown Omarchy command: omarchy debug --no-sudo --print
Run 'omarchy commands --all' to discover available commands.
```

`omarchy commands --all` lists no `debug` route.

## What I expected

Either the documented command to work, or the skill to reference the form that
does.

## The binary exists — it just isn't routed

`/usr/bin/omarchy-debug` is present and works correctly with the same flags:

```
$ omarchy-debug --no-sudo --print
Date: Sun Sep 20 12:45:41 PM BST 2026
Hostname: omarchy
Omarchy Package: omarchy 4.0.4-1
...
```

So this looks like the skill documenting a dispatcher route (`omarchy <group>`)
that was never wired up for this binary, rather than a missing feature.

## Affected files

In `/usr/share/omarchy/default/agents/skills/omarchy/`:

| File | Lines |
|---|---|
| `SKILL.md` | 222, 228, 234 |
| `contributing.md` | 26, 28 |

`SKILL.md:228` also states **"Always run `omarchy debug` with `--no-sudo
--print` flags"**, reinforcing the non-working form.

## Why it matters

The skill is symlinked into `~/.claude/skills/omarchy`, so agents follow it as
authoritative. It is also read-only and root-owned, and the skill correctly warns
against editing `/usr/share/omarchy/`, so users cannot patch it locally without
having their change wiped by the next `omarchy update`.

The sharpest edge is that `contributing.md` is specifically the *bug reporting*
guide — so the failure lands exactly when an agent is trying to collect
diagnostics for an Omarchy issue. I hit this while gathering details for #12628
and had to assemble the system information by hand.

## Suggested fix

Replace `omarchy debug` with `omarchy-debug` in the five places above, or add a
`debug` route to the dispatcher so the documented form works.

## System details

| | |
|---|---|
| Omarchy | 4.0.4-1 (stable channel) |
| Machine | Apple Macmini7,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 16:33 UTC

Proof

History & reports

Reference