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.
Using vim style navigation in omarchy-menu
Reported by eshedruf · filed Sep 29, 2025Closed upstream on 2026-02-01 by dhh, as not planned.
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
What do you need?
Currently, the only way to move up and down in the omarchy-menu is by using the arrow keys. I thought about implementing a way to also navigate the menu using Ctrl+J and Ctrl+K, in addition to the arrow keys. I’ve seen this in a few other programs (for example, fzf) that have it built in.
Since omarchy-menu uses walker, I checked for an implementation there, but it turns out the maintainer is not a big fan of this feature: https://github.com/abenz1267/walker/issues/470. So I thought maybe a small patch in omarchy could be nice.
View raw text
### What do you need? Currently, the only way to move up and down in the omarchy-menu is by using the arrow keys. I thought about implementing a way to also navigate the menu using Ctrl+J and Ctrl+K, in addition to the arrow keys. I’ve seen this in a few other programs (for example, fzf) that have it built in. Since omarchy-menu uses [walker](https://github.com/abenz1267/walker), I checked for an implementation there, but it turns out the maintainer is not a big fan of this feature: [https://github.com/abenz1267/walker/issues/470](https://github.com/abenz1267/walker/issues/470). So I thought maybe a small patch in omarchy could be nice.
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
- Fixed bypr/10934· confirmed
- Related PRpr/7345· confirmed
- Fixed bypr/7737· confirmed
- Fixed bypr/8318· confirmed
- Fixed bypr/14899· confirmed
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.