Proof Portal

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-847GitHub issuePublicDecided· Out of scope

Bar-widget plugins are not re-instantiated on hot reload: the widget silently vanishes from the bar until the shell is restarted

Reported by kstorm12 · filed Sep 7, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

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

Bar-widget plugins are not re-instantiated on hot reload: the widget silently vanishes from the bar until the shell is restartedrevision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

Editing or cloning a plugin whose kind is bar-widget triggers the shell's hot reload, but the widget is never re-instantiated. It simply disappears from the bar, with no warning of any kind: nothing in the journal, no QML error, no visible failure. omarchy restart shell brings it back.

Service plugins hot-reload correctly in the same operation, which is what makes this so hard to spot: the reload clearly did something.

Steps to reproduce

  1. omarchy plugin clone omarchy.indicators
  2. Watch the journal: journalctl --user -f | grep -i "reloading\|qml"
  3. Touch or edit any file in ~/.config/omarchy/plugins/<user>.indicators/

Observed, on every save:

DEBUG qml: Local plugin changed, reloading: kyle.indicators
DEBUG qml: omarchy idle ... service-ready

The service re-initializes each time. The widget does not. I confirmed this by putting a console.log in the widget's Component.onCompleted: it never fired across five consecutive hot reloads, and the entire indicator cluster was missing from the bar the whole time. After omarchy restart shell the same build logged it immediately:

DEBUG qml: DEBUG Indicators widget loaded, entries=["Dictation","ScreenRecording","Reminder","NightLight","Dnd","StayAwake"]

Expected: the widget comes back after a hot reload, the way the service does.
Actual: it is gone until the shell is restarted.

Why it matters

The absence is completely silent, so the natural conclusion is that your edit did not work, and you keep editing. A QML syntax error does log (WARN qml: Plugin widget <id> failed: ...: Syntax error), which sets the wrong expectation: you learn to trust the journal, and then this case tells you nothing.

I lost most of a debugging session to this while working around #10698. The widget had been absent since the clone was created, and every signal available said the plugin had loaded.

System

  • Omarchy 4.0.2-1
  • Quickshell 0.3.1 (Arch)
  • Hyprland 0.56.2
  • AMD Ryzen 7 7735HS / Radeon 680M
  • Linux 7.1.9-arch1-2
View raw text
### What happened

Editing or cloning a plugin whose kind is `bar-widget` triggers the shell's hot reload, but the widget is never re-instantiated. It simply disappears from the bar, with **no warning of any kind**: nothing in the journal, no QML error, no visible failure. `omarchy restart shell` brings it back.

Service plugins hot-reload correctly in the same operation, which is what makes this so hard to spot: the reload clearly did *something*.

### Steps to reproduce

1. `omarchy plugin clone omarchy.indicators`
2. Watch the journal: `journalctl --user -f | grep -i "reloading\|qml"`
3. Touch or edit any file in `~/.config/omarchy/plugins/<user>.indicators/`

Observed, on every save:

```
DEBUG qml: Local plugin changed, reloading: kyle.indicators
DEBUG qml: omarchy idle ... service-ready
```

The service re-initializes each time. The widget does not. I confirmed this by putting a `console.log` in the widget's `Component.onCompleted`: it never fired across five consecutive hot reloads, and the entire indicator cluster was missing from the bar the whole time. After `omarchy restart shell` the same build logged it immediately:

```
DEBUG qml: DEBUG Indicators widget loaded, entries=["Dictation","ScreenRecording","Reminder","NightLight","Dnd","StayAwake"]
```

Expected: the widget comes back after a hot reload, the way the service does.
Actual: it is gone until the shell is restarted.

### Why it matters

The absence is completely silent, so the natural conclusion is that your edit did not work, and you keep editing. A QML *syntax* error does log (`WARN qml: Plugin widget <id> failed: ...: Syntax error`), which sets the wrong expectation: you learn to trust the journal, and then this case tells you nothing.

I lost most of a debugging session to this while working around #10698. The widget had been absent since the clone was created, and every signal available said the plugin had loaded.

### System

- Omarchy 4.0.2-1
- Quickshell 0.3.1 (Arch)
- Hyprland 0.56.2
- AMD Ryzen 7 7735HS / Radeon 680M
- Linux 7.1.9-arch1-2

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 11:06 UTC