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.
Create universally searchable Omarchy Menu
Reported by ryanrhughes · filed Oct 24, 2025Closed upstream on 2026-07-18 by dhh, as a duplicate of #2807 (R-3488). 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
What do you need?
Walker / Elephant have support for a menu syntax (https://benz.gitbook.io/walker/customization/custom-menus) that allows for a much more robust and modular setup than we have currently in omarchy-menu.
The current structure is can make merges difficult at times but also requires manual navigation of each level.
In the latest version of Walker, @abenz1267 created a new feature called Sets that should allow us to change this entirely.
Todos
- Convert the existing menus to the Walker menu syntax
- Update the layout to support nerdicons as well
- Utilize Sets to group the menu and allow for universal search
- Refine the layout to ensure that there's an indicator of where an item came from to distinguish
Install > Style > ThemefromRemove > Style > Theme
Nerdicons Layout Add References
Add to layout:
<child>
<object class="GtkLabel" id="ItemImageFont">
<style>
<class name="item-image-text"></class>
</style>
<property name="width-chars">2</property>
</object>
</child>Usage Example
name = "omarchycapture"
name_pretty = "Capture"
[[entries]]
text = "Screenshot"
submenu = "omarchyscreenshot"
icon = ""
[[entries]]
text = "Screenrecord"
submenu = "omarchyscreenrecord"
icon = ""
[[entries]]
text = "Color"
actions = { "pick" = "pkill hyprpicker || hyprpicker -a" }
icon = ""View raw text
### What do you need?
Walker / Elephant have support for a menu syntax (https://benz.gitbook.io/walker/customization/custom-menus) that allows for a much more robust and modular setup than we have currently in [omarchy-menu](https://github.com/basecamp/omarchy/blob/master/bin/omarchy-menu).
The current structure is can make merges difficult at times but also requires manual navigation of each level.
In the latest version of Walker, @abenz1267 created a new feature called [Sets](https://benz.gitbook.io/walker/customization/general-config#sets) that should allow us to change this entirely.
### Todos
- [ ] Convert the existing menus to the Walker menu syntax
- [ ] Update the layout to support nerdicons as well
- [ ] Utilize Sets to group the menu and allow for universal search
- [ ] Refine the layout to ensure that there's an indicator of where an item came from to distinguish `Install > Style > Theme` from `Remove > Style > Theme`
### Nerdicons Layout Add References
**Add to layout:**
```
<child>
<object class="GtkLabel" id="ItemImageFont">
<style>
<class name="item-image-text"></class>
</style>
<property name="width-chars">2</property>
</object>
</child>
```
**Usage Example**
```
name = "omarchycapture"
name_pretty = "Capture"
[[entries]]
text = "Screenshot"
submenu = "omarchyscreenshot"
icon = ""
[[entries]]
text = "Screenrecord"
submenu = "omarchyscreenrecord"
icon = ""
[[entries]]
text = "Color"
actions = { "pick" = "pkill hyprpicker || hyprpicker -a" }
icon = ""
```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.