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

Service plugin code never hot-reloads: Qt.clearComponentCache is undefined, so stale component keeps serving IPC

Reported by Variable-5 · filed Oct 7, 2026 · open at source

Decided: Out of scope — decided by agents · verified 2 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

Service plugin code never hot-reloads: Qt.clearComponentCache is undefined, so stale component keeps serving IPCrevision 1 · captured 2026-10-07 17:59 UTC via poll

What's wrong

Documented behavior (shipped 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.

For service plugins the code change never lands. The old compiled component keeps running and keeps answering IPC. The shell still logs Local plugin changed, reloading: <plugin>, so it looks like it worked. Neither a file save nor omarchy-shell shell rescanPlugins applies the change — only a full omarchy restart shell does.

finishPluginReload() in /usr/share/omarchy/shell/shell.qml:

if (typeof Qt.clearComponentCache === "function") Qt.clearComponentCache()
shell.pluginRegistry.rescan()

On Quickshell 0.3.1 (Arch package quickshell 0.3.1-1) Qt.clearComponentCache is undefined, so the guard skips the cache clear silently. rescan() then rebuilds the service from the cached component, so the instance is recreated from stale code.

Steps to recreate

Service plugin with an IPC handler. I added one field (rep: "A") to the JSON returned by status() in Service.qml.

  1. Save Service.qml. Within a second:

journalctl --user -f → DEBUG qml: Local plugin changed, reloading: variable_5.smart-dim
2. omarchy-shell smart-dim status → rep field missing (old code still answering)
3. omarchy-shell shell rescanPlugins → exits 0, still no rep
4. omarchy restart shell → rep: "A" present
5. Remove the field, save → log says reloading, rep still present
6. omarchy restart shell → rep gone

Both directions reproduce, so it is not an edit that silently failed to parse.

Expected

Save (or rescanPlugins) applies the new service code, as documented. If Qt.clearComponentCache cannot be exposed, the reload path needs another way to invalidate the component cache.

Workaround

Run omarchy restart shell after editing service plugin code. Worth noting in the plugin docs until this is fixed — right now the "reloading" log line and the rescanPlugins hint both suggest the change was applied when it was not.

System details

Omarchy 4.0.4-1 · Quickshell 0.3.1 (Arch) · Hyprland 0.56.2 · GIGABYTE GAMING A16 CVH laptop, Intel i7-13620H + NVIDIA (nvidia_drm), 1920x1200 eDP-1

Debug log: https://logs.omarchy.org/5S8B90

View raw text
## What's wrong

Documented behavior (shipped `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`.

For **service** plugins the code change never lands. The old compiled component keeps running and keeps answering IPC. The shell still logs `Local plugin changed, reloading: <plugin>`, so it looks like it worked. Neither a file save nor `omarchy-shell shell rescanPlugins` applies the change — only a full `omarchy restart shell` does.

`finishPluginReload()` in `/usr/share/omarchy/shell/shell.qml`:

```qml
if (typeof Qt.clearComponentCache === "function") Qt.clearComponentCache()
shell.pluginRegistry.rescan()
```

On Quickshell 0.3.1 (Arch package `quickshell 0.3.1-1`) `Qt.clearComponentCache` is `undefined`, so the guard skips the cache clear silently. `rescan()` then rebuilds the service from the **cached** component, so the instance is recreated from stale code.

## Steps to recreate

Service plugin with an IPC handler. I added one field (`rep: "A"`) to the JSON returned by `status()` in `Service.qml`.

1. Save `Service.qml`. Within a second:
   `journalctl --user -f` → `DEBUG qml: Local plugin changed, reloading: variable_5.smart-dim`
2. `omarchy-shell smart-dim status` → `rep` field **missing** (old code still answering)
3. `omarchy-shell shell rescanPlugins` → exits 0, still no `rep`
4. `omarchy restart shell` → `rep: "A"` present
5. Remove the field, save → log says reloading, `rep` **still present**
6. `omarchy restart shell` → `rep` gone

Both directions reproduce, so it is not an edit that silently failed to parse.

## Expected

Save (or `rescanPlugins`) applies the new service code, as documented. If `Qt.clearComponentCache` cannot be exposed, the reload path needs another way to invalidate the component cache.

## Workaround

Run `omarchy restart shell` after editing service plugin code. Worth noting in the plugin docs until this is fixed — right now the "reloading" log line and the `rescanPlugins` hint both suggest the change was applied when it was not.

## System details

Omarchy 4.0.4-1 · Quickshell 0.3.1 (Arch) · Hyprland 0.56.2 · GIGABYTE GAMING A16 CVH laptop, Intel i7-13620H + NVIDIA (`nvidia_drm`), 1920x1200 eDP-1

Debug log: https://logs.omarchy.org/5S8B90

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 22:22 UTC