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.
Omarchy Box: Test and demo Omarchy in a virtual machine
Reported by dylanbr · filed Aug 14, 2025Closed upstream on 2025-08-22 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
I submitted some PRs to Omarchy, and after being merged, there were still lingering issues. It got me thinking that it would be nice to have an easy way to test a full build after making changes.
Right now it's a proof of concept, and I haven't actually managed to get a build 100% complete (some minor patches to Omarchy may be needed), but it's far enough along that I'd like to share it.
You can check it out at dylanbr/omarchy-box.
It uses qemu, so other than testing the build, it may be usable to try out or demo Omarchy. I'm not sure yet what the performance will be like though. I haven't actually had a chance to run it on a Linux machine yet, only having access to Mac hardware currently, but in theory it should work on Linux without an issue.
Looking forward to your feedback!
View raw text
I submitted some PRs to Omarchy, and after being merged, there were still lingering issues. It got me thinking that it would be nice to have an easy way to test a full build after making changes. Right now it's a proof of concept, and I haven't actually managed to get a build 100% complete (some minor patches to Omarchy may be needed), but it's far enough along that I'd like to share it. You can check it out at [dylanbr/omarchy-box](https://github.com/dylanbr/omarchy-box). It uses `qemu`, so other than testing the build, it may be usable to try out or demo Omarchy. I'm not sure yet what the performance will be like though. I haven't actually had a chance to run it on a Linux machine yet, only having access to Mac hardware currently, but in theory it should work on Linux without an issue. Looking forward to your feedback!
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.