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.
plugins.md: service-plugin constant edits need `omarchy restart shell`, not `rescanPlugins`
Reported by johnfire · filed Sep 3, 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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
What happened
shell/plugins/.../README-adjacent docs and the packaged agent skill both state that saved changes under ~/.config/omarchy/plugins/ reload automatically. For service plugins that is not true of QML readonly property constants: omarchy-shell shell rescanPlugins reports the plugin as active while the old values stay live.
Concretely, in default/agents/skills/omarchy/plugins.md:
Saving a file anywhere under~/.config/omarchy/plugins/reloads plugin code automatically. If a change somehow fails to apply, force a reload withomarchy-shell shell rescanPlugins.
Following that guidance on a cloned notifications service leaves the old behaviour running, with no error and no indication anything was missed.
Steps to reproduce
omarchy plugin clone omarchy.notifications- Edit
~/.config/omarchy/plugins/<user>.notifications/Service.qmland change the popup duration constants:
readonly property int lowPopupDuration: 5000 -> 3000
readonly property int normalPopupDuration: 8000 -> 3000
readonly property int maxPopupDuration: 30000 -> 3000omarchy-shell shell rescanPluginsnotify-send "test" "how long do I last"
Expected
The toast lasts 3s, or the rescan reports that it could not apply the change.
Actual
The toast lasts the previous duration. omarchy plugin list shows the cloned plugin enabled the whole time, so nothing signals that the edit did not take.
omarchy restart shell applies it. The service object appears to hold its readonly property values from construction, so a rescan that does not reconstruct the service cannot pick them up.
Measured
Timed by watching the per-popup state file under ~/.local/state/omarchy/notifications/ (one file exists exactly as long as its toast is on screen):
| step | popup lifetime |
|---|---|
constants set to 3000, after rescanPlugins | 8.04s (old value) |
same, after omarchy restart shell | 2.99s |
Isolated further: with the clone already active, changing the constants to 6000 and running only rescanPlugins still produced 2.99s — the previously loaded value, not the edited one.
Suggested fix
Either make rescanPlugins reconstruct service plugins, or amend plugins.md to say that the automatic reload covers widget code while service-plugin constants need omarchy restart shell. The docs change alone would have saved the confusion.
System
- Omarchy 4.0.2-1
- Hyprland 0.56.2
- quickshell 0.3.1-1
- Kernel 7.1.9-arch1-2
- AMD Ryzen AI 9 HX 370 / Radeon 890M
View raw text
## What happened `shell/plugins/.../README`-adjacent docs and the packaged agent skill both state that saved changes under `~/.config/omarchy/plugins/` reload automatically. For **service plugins** that is not true of QML `readonly property` constants: `omarchy-shell shell rescanPlugins` reports the plugin as active while the old values stay live. Concretely, in `default/agents/skills/omarchy/plugins.md`: > Saving a file anywhere under `~/.config/omarchy/plugins/` reloads plugin code automatically. If a change somehow fails to apply, force a reload with `omarchy-shell shell rescanPlugins`. Following that guidance on a cloned notifications service leaves the old behaviour running, with no error and no indication anything was missed. ## Steps to reproduce 1. `omarchy plugin clone omarchy.notifications` 2. Edit `~/.config/omarchy/plugins/<user>.notifications/Service.qml` and change the popup duration constants: ``` readonly property int lowPopupDuration: 5000 -> 3000 readonly property int normalPopupDuration: 8000 -> 3000 readonly property int maxPopupDuration: 30000 -> 3000 ``` 3. `omarchy-shell shell rescanPlugins` 4. `notify-send "test" "how long do I last"` ## Expected The toast lasts 3s, or the rescan reports that it could not apply the change. ## Actual The toast lasts the previous duration. `omarchy plugin list` shows the cloned plugin enabled the whole time, so nothing signals that the edit did not take. `omarchy restart shell` applies it. The service object appears to hold its `readonly property` values from construction, so a rescan that does not reconstruct the service cannot pick them up. ### Measured Timed by watching the per-popup state file under `~/.local/state/omarchy/notifications/` (one file exists exactly as long as its toast is on screen): | step | popup lifetime | |---|---| | constants set to 3000, after `rescanPlugins` | 8.04s (old value) | | same, after `omarchy restart shell` | 2.99s | Isolated further: with the clone already active, changing the constants to 6000 and running only `rescanPlugins` still produced 2.99s — the previously loaded value, not the edited one. ## Suggested fix Either make `rescanPlugins` reconstruct service plugins, or amend `plugins.md` to say that the automatic reload covers widget code while service-plugin constants need `omarchy restart shell`. The docs change alone would have saved the confusion. ## System - Omarchy 4.0.2-1 - Hyprland 0.56.2 - quickshell 0.3.1-1 - Kernel 7.1.9-arch1-2 - AMD Ryzen AI 9 HX 370 / Radeon 890M
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.
- Out of scopeDecided by agents · verified · 2026-10-09 10:39 UTC