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 extensions: overriding an existing id resets its icon and label
Reported by ahmadtv · filed Sep 12, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #11211 (R-711). 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
System details
Omarchy 4.0.3 (same code on current quattro).
What's wrong?
~/.config/omarchy/extensions/omarchy-menu.jsonc says: "Reuse an existing id to override/extend it … Existing fields are kept unless overridden." They aren't. MenuModel.parseMenuJsonc runs normalizeItem on every user entry, which fills in defaults (label: value.label || id, icon: value.icon || "", …), and mergeMenuSources then copies those defaults over the built-in row. So an override that only changes action shows the row as its bare id, with no icon.
To reproduce, add this to ~/.config/omarchy/extensions/omarchy-menu.jsonc:
"trigger.capture.screenrecord.no-audio": {"action": "omarchy-capture-screenrecording --resolution=1920x1080"},Under Capture → Screenrecord the row now reads trigger.capture.screenrecord.no-audio, with no icon. The template's own About example sets icon, label and action, which hides the problem.
A possible fix: merge the raw user object onto the raw default object before normalizing, or have normalizeItem fill defaults only for ids that don't exist in the default menu.
View raw text
### System details
Omarchy 4.0.3 (same code on current `quattro`).
### What's wrong?
`~/.config/omarchy/extensions/omarchy-menu.jsonc` says: "Reuse an existing id to override/extend it … Existing fields are kept unless overridden." They aren't. `MenuModel.parseMenuJsonc` runs `normalizeItem` on every user entry, which fills in defaults (`label: value.label || id`, `icon: value.icon || ""`, …), and `mergeMenuSources` then copies those defaults over the built-in row. So an override that only changes `action` shows the row as its bare id, with no icon.
To reproduce, add this to `~/.config/omarchy/extensions/omarchy-menu.jsonc`:
```jsonc
"trigger.capture.screenrecord.no-audio": {"action": "omarchy-capture-screenrecording --resolution=1920x1080"},
```
Under Capture → Screenrecord the row now reads `trigger.capture.screenrecord.no-audio`, with no icon. The template's own About example sets icon, label and action, which hides the problem.
A possible fix: merge the raw user object onto the raw default object before normalizing, or have `normalizeItem` fill defaults only for ids that don't exist in the default menu.
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/10007· confirmed
- Fixed bypr/12255· confirmed
- Fixed bypr/9695· confirmed
- Fixed bypr/15117· 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.