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.
Menu prompts don't allow "+" character
Reported by ty-davis · filed Aug 20, 2026 · open at source
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?
- 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. So far: in the audited area (menu) — decided by agents · verified; matches no known issue — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.
Original report
System details
Lenovo Legion, i9-14900, NVidia 4060 Max-Q, Omarchy 4.0.0
What's wrong?
When searching for something in any omarchy menu, you are not permitted to input the "+" character (may be others that aren't allowed, but I couldn't find it). This is really only problematic when searching through keybinds because you largely can't search for a keybind by it's hotkey (e.g. SUPER SHIFT + RETURN is unsearchable because you can't put + in the query)
View raw text
### System details Lenovo Legion, i9-14900, NVidia 4060 Max-Q, Omarchy 4.0.0 ### What's wrong? When searching for something in any omarchy menu, you are not permitted to input the "+" character (may be others that aren't allowed, but I couldn't find it). This is really only problematic when searching through keybinds because you largely can't search for a keybind by it's hotkey (e.g. SUPER SHIFT + RETURN is unsearchable because you can't put + in the query)
Also reported as
R-1617 is the earliest report of this defect, filed Aug 20, 2026. 1 later report describes the same defect.
- Aug 20, 2026R-1617 · this report— the original
- ·Decided by agents · verified
Open upstream.
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/7659· confirmed
- Fixed bypr/14662· confirmed
- Fixed bypr/8023· 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.
- Decided by agents · verified: in the audited area (menu)
- Decided by agents · verified: matches no known issue
The outcome (valid, duplicate, not a bug, …) is not decided yet.