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.
Instructions for running off a fork
Reported by logannc · filed Aug 17, 2025Closed upstream on 2025-08-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
Not sure where to put this as this repo doesn't seem to contain the manual - where is that anyway?
The Omarchy update mechanism checks https://github.com/basecamp/omarchy for tags newer than what is in the local git clone.
I expect you can fork omarchy, switch git remotes to the fork ,and stay up to date by updating the fork then updating omarchy normally.
Confirming this with an entry in the manual might be nice.
Why would we want this? Well, perhaps there are things you want to edit in Omarchy that both are not worth making configurable and should not be upstreamed. e.g., https://github.com/basecamp/omarchy/blob/master/logo.txt so the screensavers show different text or something.
View raw text
Not sure where to put this as this repo doesn't seem to contain the manual - where is that anyway? The Omarchy update mechanism checks https://github.com/basecamp/omarchy for tags newer than what is in the local git clone. I expect you can fork omarchy, switch git remotes to the fork ,and stay up to date by updating the fork then updating omarchy normally. Confirming this with an entry in the manual might be nice. Why would we want this? Well, perhaps there are things you want to edit in Omarchy that both are not worth making configurable _and_ should not be upstreamed. e.g., https://github.com/basecamp/omarchy/blob/master/logo.txt so the screensavers show different text or something.
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.