Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-5088GitHub issuePublicReceived

Local plugin edits are never applied — "Local plugin changed, reloading" is logged but old code keeps running

Reported by NiklasNeugebauer · filed Sep 15, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #6981 (R-1835). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Local plugin edits are never applied — "Local plugin changed, reloading" is logged but old code keeps runningrevision 1 · captured 2026-10-04 12:10 UTC via poll

What happened

Editing a local plugin under ~/.config/omarchy/plugins/<id>/ logs
Local plugin changed, reloading: <id> but the running shell keeps executing
the previous code. Neither the file watcher nor `omarchy-shell shell
rescanPlugins applies the change. Only a full omarchy restart shell` does.

Expected

Saving a local plugin file applies the change, as the reload log says it did.

Steps to reproduce

  1. omarchy plugin clone omarchy.clock (any bar-widget plugin works).
  2. Add a probe to the clone's entry point BarWidget.qml:

Component.onCompleted: console.log("PROBE-WIDGET-LOADED")
3. Save, and watch journalctl --user -f. It logs
Local plugin changed, reloading: <id> — repeatedly, 4-16x per save here.
The probe never fires.
4. omarchy-shell shell rescanPlugins — returns rc=0. The probe still never fires.
5. omarchy restart shell — the probe fires once, immediately.

Same result for non-entry-point files in the plugin, e.g. a Panel.qml
pulled in by the widget's Loader.

Why it matters

The log claims a reload that did not happen, so stale plugin code is
indistinguishable from live code. An edit that actually fixes a bug appears to
change nothing, which sends you looking in the wrong place. I ran into this
while working on a clone of the clock plugin: the fix was correct from the
first attempt, but nothing applied it, so it read as a wrong diagnosis until I
restarted the shell.

System

  • Omarchy 4.0.3-1
  • Hyprland 0.56.2
  • Quickshell 0.3.1 (Arch)
  • AMD Ryzen 7 7840U / Radeon 780M (Phoenix1)
View raw text
### What happened

Editing a local plugin under `~/.config/omarchy/plugins/<id>/` logs
`Local plugin changed, reloading: <id>` but the running shell keeps executing
the previous code. Neither the file watcher nor `omarchy-shell shell
rescanPlugins` applies the change. Only a full `omarchy restart shell` does.

### Expected

Saving a local plugin file applies the change, as the reload log says it did.

### Steps to reproduce

1. `omarchy plugin clone omarchy.clock` (any bar-widget plugin works).
2. Add a probe to the clone's entry point `BarWidget.qml`:
   `Component.onCompleted: console.log("PROBE-WIDGET-LOADED")`
3. Save, and watch `journalctl --user -f`. It logs
   `Local plugin changed, reloading: <id>` — repeatedly, 4-16x per save here.
   The probe never fires.
4. `omarchy-shell shell rescanPlugins` — returns rc=0. The probe still never fires.
5. `omarchy restart shell` — the probe fires once, immediately.

Same result for non-entry-point files in the plugin, e.g. a `Panel.qml`
pulled in by the widget's `Loader`.

### Why it matters

The log claims a reload that did not happen, so stale plugin code is
indistinguishable from live code. An edit that actually fixes a bug appears to
change nothing, which sends you looking in the wrong place. I ran into this
while working on a clone of the clock plugin: the fix was correct from the
first attempt, but nothing applied it, so it read as a wrong diagnosis until I
restarted the shell.

### System

- Omarchy 4.0.3-1
- Hyprland 0.56.2
- Quickshell 0.3.1 (Arch)
- AMD Ryzen 7 7840U / Radeon 780M (Phoenix1)

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.