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

Docs and scripts still point at basecamp/omarchy; agent bug-reporting guide sends duplicate searches to a repo that cannot be searched

Reported by Yannick-Pinta · filed Aug 31, 2026 · 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

Docs and scripts still point at basecamp/omarchy; agent bug-reporting guide sends duplicate searches to a repo that cannot be searchedrevision 1 · captured 2026-09-28 21:24 UTC via poll

What happened

The repo has moved from basecamp/omarchy to omacom/omarchy, but 11 files still reference the old path on main:

bin/omarchy-channel-set
bin/omarchy-update-confirm
bin/omarchy-upgrade-to-quattro
default/agents/skills/diagnose-crash/reporting.md
default/agents/skills/omarchy/contributing.md
default/hypr/apps/jetbrains.lua
default/systemd/user/omarchy-speaker-tuning.service
.github/ISSUE_TEMPLATE/config.yml
manual/30-updates.md
manual/49-omarchy-on.md
test/shell.d/channel-test.sh

Most of this is harmless — one part is not

GitHub's rename redirect covers almost every use, so I want to be clear about what is and isn't broken:

# redirects fine — no functional breakage
$ gh repo view basecamp/omarchy --json nameWithOwner
{"nameWithOwner":"omacom/omarchy"}
$ git ls-remote https://github.com/basecamp/omarchy HEAD
b686ed892d9c3020c3336203f6d34cc75b544e2b        HEAD

# does NOT redirect — hard failure
$ gh search issues --repo basecamp/omarchy "test" --limit 1
Invalid search query "( test ) repo:basecamp/omarchy type:issue".
The listed users and repositories cannot be searched either because the resources
do not exist or you do not have permission to view them.

So omarchy-channel-set's git clone and omarchy-update-confirm's releases URL keep working; they are just cosmetically stale.

The search failure matters more than it looks, because default/agents/skills/omarchy/contributing.md is the file an AI agent reads to learn how to report an Omarchy bug. It sends the agent to --repo basecamp/omarchy, where duplicate-checking fails outright. An agent that treats that failure as "no duplicates exist" will file duplicates. I hit exactly this an hour ago: my duplicate search returned nothing, and I only found the real repo by checking gh repo view.

.github/ISSUE_TEMPLATE/config.yml is worth a look too, since it steers people at report time.

Expected

References updated to omacom/omarchy, with priority on the two files that direct bug reports: default/agents/skills/omarchy/contributing.md and .github/ISSUE_TEMPLATE/config.yml.

Notes

  • Verified against main via the contents API, not just my local package, so this is not a packaging lag.
  • Found on Omarchy 4.0.2-1.
  • Happy to send a PR if a straight find-and-replace is the shape you want — some of those hits may be deliberate, so I would rather ask than guess.
View raw text
### What happened

The repo has moved from `basecamp/omarchy` to `omacom/omarchy`, but 11 files still reference the old path on `main`:

```
bin/omarchy-channel-set
bin/omarchy-update-confirm
bin/omarchy-upgrade-to-quattro
default/agents/skills/diagnose-crash/reporting.md
default/agents/skills/omarchy/contributing.md
default/hypr/apps/jetbrains.lua
default/systemd/user/omarchy-speaker-tuning.service
.github/ISSUE_TEMPLATE/config.yml
manual/30-updates.md
manual/49-omarchy-on.md
test/shell.d/channel-test.sh
```

### Most of this is harmless — one part is not

GitHub's rename redirect covers almost every use, so I want to be clear about what is and isn't broken:

```bash
# redirects fine — no functional breakage
$ gh repo view basecamp/omarchy --json nameWithOwner
{"nameWithOwner":"omacom/omarchy"}
$ git ls-remote https://github.com/basecamp/omarchy HEAD
b686ed892d9c3020c3336203f6d34cc75b544e2b        HEAD

# does NOT redirect — hard failure
$ gh search issues --repo basecamp/omarchy "test" --limit 1
Invalid search query "( test ) repo:basecamp/omarchy type:issue".
The listed users and repositories cannot be searched either because the resources
do not exist or you do not have permission to view them.
```

So `omarchy-channel-set`'s `git clone` and `omarchy-update-confirm`'s releases URL keep working; they are just cosmetically stale.

The search failure matters more than it looks, because `default/agents/skills/omarchy/contributing.md` is the file an AI agent reads to learn how to report an Omarchy bug. It sends the agent to `--repo basecamp/omarchy`, where duplicate-checking fails outright. An agent that treats that failure as "no duplicates exist" will file duplicates. I hit exactly this an hour ago: my duplicate search returned nothing, and I only found the real repo by checking `gh repo view`.

`.github/ISSUE_TEMPLATE/config.yml` is worth a look too, since it steers people at report time.

### Expected

References updated to `omacom/omarchy`, with priority on the two files that direct bug reports: `default/agents/skills/omarchy/contributing.md` and `.github/ISSUE_TEMPLATE/config.yml`.

### Notes

- Verified against `main` via the contents API, not just my local package, so this is not a packaging lag.
- Found on Omarchy 4.0.2-1.
- Happy to send a PR if a straight find-and-replace is the shape you want — some of those hits may be deliberate, so I would rather ask than guess.

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 02:25 UTC