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 skill docs reference basecamp/omarchy; `gh search` fails against the renamed repo
Reported by phren0logy · filed Sep 1, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #9376 (R-1166). GitHub close reason: completed.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
Omarchy 4.0.2-1, AMD RYZEN AI MAX+ 395 w/ Radeon 8060S (amdgpu), Hyprland 0.56.2, Linux 7.1.9-arch1-2.
What's wrong?
The bundled agent skills still point at basecamp/omarchy. The repository is now omacom/omarchy. GitHub redirects cover most gh subcommands, but `gh search` does not follow the rename — so the duplicate-check step these guides themselves prescribe fails:
$ gh search issues --repo basecamp/omarchy "brightness ddc" --limit 5
Invalid search query "( \"brightness ddc\" ) repo:basecamp/omarchy".
The listed users and repositories cannot be searched either because the resources
do not exist or you do not have permission to view them.
$ gh search issues --repo omacom/omarchy "brightness ddc" --limit 5
pr omacom/omarchy 4841 closed Fall back to DDC/CI for brightness on external monitorsThe failure mode is what makes this worth fixing: an agent follows contributing.md, searches for existing reports, gets "the resources do not exist", reasonably concludes nothing has been filed, and opens a duplicate.
That is not hypothetical — it nearly happened while investigating a DDC brightness problem today. The search only surfaced the already-open #8931 after switching to the current repo name.
diagnose-crash/reporting.md:43 is the sharpest case, since the stale name sits inside the search command itself:
gh search issues --repo basecamp/omarchy "<program> crash"Affected files
9 references across two shipped skills:
| file | lines |
|---|---|
default/agents/skills/omarchy/contributing.md | 6, 12, 46, 57 |
default/agents/skills/diagnose-crash/reporting.md | 43, 44, 62, 77, 85 |
Expected
Skill docs reference omacom/omarchy, so the gh search / gh issue examples work as written.
Actual
They reference basecamp/omarchy; gh search fails outright, and duplicate-checking silently returns nothing.
View raw text
## System details Omarchy 4.0.2-1, AMD RYZEN AI MAX+ 395 w/ Radeon 8060S (amdgpu), Hyprland 0.56.2, Linux 7.1.9-arch1-2. ## What's wrong? The bundled agent skills still point at `basecamp/omarchy`. The repository is now `omacom/omarchy`. GitHub redirects cover most `gh` subcommands, but **`gh search` does not follow the rename** — so the duplicate-check step these guides themselves prescribe fails: ```text $ gh search issues --repo basecamp/omarchy "brightness ddc" --limit 5 Invalid search query "( \"brightness ddc\" ) repo:basecamp/omarchy". The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them. $ gh search issues --repo omacom/omarchy "brightness ddc" --limit 5 pr omacom/omarchy 4841 closed Fall back to DDC/CI for brightness on external monitors ``` The failure mode is what makes this worth fixing: an agent follows `contributing.md`, searches for existing reports, gets *"the resources do not exist"*, reasonably concludes nothing has been filed, and opens a duplicate. That is not hypothetical — it nearly happened while investigating a DDC brightness problem today. The search only surfaced the already-open #8931 after switching to the current repo name. `diagnose-crash/reporting.md:43` is the sharpest case, since the stale name sits inside the search command itself: ```bash gh search issues --repo basecamp/omarchy "<program> crash" ``` ## Affected files 9 references across two shipped skills: | file | lines | | --- | --- | | `default/agents/skills/omarchy/contributing.md` | 6, 12, 46, 57 | | `default/agents/skills/diagnose-crash/reporting.md` | 43, 44, 62, 77, 85 | ## Expected Skill docs reference `omacom/omarchy`, so the `gh search` / `gh issue` examples work as written. ## Actual They reference `basecamp/omarchy`; `gh search` fails outright, and duplicate-checking silently returns nothing.
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.
No decision has been recorded yet.