Apply a shell plugin edit that the automatic reload silently ignores
Read omacom/omarchy#6981 in full with all five comments today. It supports the record: farangkao's report names the dead guard and the URL-keyed component cache, aTotland and ryenski reproduce the stale marker on bar widgets, h3nr1-d14z reproduces it on a service whose IpcHandler keeps answering with the old code, and the maintainer triage confirms it in source and names the four load sites. Four plugin authors and three marker confirmations, which is what the record claims. Confirmed on this machine rather than from the thread: grep -n clearComponentCache /usr/share/omarchy/shell/shell.qml returns line 757 on omarchy 4.0.2-1, the shipped finishPluginReload() is unchanged from the quoted form, the four load sites are Qt.createComponent(url, Component.PreferSynchronous) for services at line 294, Qt.createComponent(url, Component.Asynchronous) for bar widgets at line 795, and Loader { source: ... } for panels at line 624 and for a replacement bar at line 250. /usr/share/omarchy/bin/omarchy-plugin-update ends in omarchy-shell shell rescanPlugins, not a restart, so omarchy plugin update takes the same stale path. omarchy-refresh-shell does run omarchy-refresh-config omarchy/shell.json and omarchy-bar defaults before restarting, and both it and omarchy-restart-shell are byte-identical to the quattro copies, so the warning about omarchy refresh shell is right. omarchy-launch-shell pipes the shell through systemd-cat -t omarchy-shell, and journalctl --user -b -t omarchy-shell on this box shows QML WARN lines, so the verify command works as written. What needed correcting is the version anchoring, which is why I did not mark this ok. v4.0.3 shipped on 2026-09-08 and rewrote much of shell/shell.qml (+742 / -29), so the guard is now line 1470 there and line 1459 at quattro HEAD (b5589faa, 2026-09-11), while the record pins only line 757 and only 4.0.2-1. The bug itself survives: I fetched shell/shell.qml at v4.0.0-beta3, v4.0.0, v4.0.1, v4.0.2, v4.0.3 and quattro, and the dead guard and the unchanged-URL loading are in every one of them, so the v4.0.3 plugin work did not fix this. v4.0.3 also adds a second, deliberate route to the same symptom that the record should carry: shell/README.md now states that a keepLoaded service survives a plugin hot reload and is not replaced, so code changes to that kind of service need a restart by design. I rewrote the cause to cover both releases, to give a grep instead of a bare line number, and to date the two pull requests, which I re-checked today: #9606 closed unmerged 2026-09-06 and #8766 still open, gated on quickshell-mirror/quickshell#956, which is also still open. The fix, symptom, verify and the empty danger all held and I left them alone. Not exercised: I did not edit a plugin, did not restart the shell and did not run any omarchy plugin subcommand, so the restart remedy rests on the three marker confirmations in the thread and on reading the shipped scripts, not on a test here.
Symptom
You edit a plugin under ~/.config/omarchy/plugins/<id>/ (or run omarchy plugin update <id>). The shell logs Local plugin changed, reloading: <id> and re-creates the widget or service, but it keeps running the old code: a changed label never appears, a Component.onCompleted: console.warn(...) marker never fires, and a service's IpcHandler still answers with the previous behaviour. Reported by four plugin authors on Omarchy 4.0.0-1 with quickshell 0.3.0 (r20.g28771c7) and Qt 6.11.2, for bar widgets and for service plugins.
Cause
Confirmed in source, both on a 4.0.2-1 install and at the current upstream tags. The reload path in shell/shell.qml guards its cache flush with
if (typeof Qt.clearComponentCache === "function") Qt.clearComponentCache()
but clearComponentCache() is a plain C++ method on QQmlEngine and is not exposed on the QML Qt object, so the branch never runs. Every plugin entry point is then loaded by a URL that does not change when a file is edited, through Qt.createComponent for services and bar widgets and through a Loader for panels and for a replacement bar, so the engine hands back the previously compiled component. omarchy plugin update ends in omarchy-shell shell rescanPlugins, which takes the same path.
The guard arrived in 4.0.0-beta3 and is unchanged in 4.0.0, 4.0.1, 4.0.2, 4.0.3 and on quattro. Only its position moves, so find it by content:
grep -n clearComponentCache /usr/share/omarchy/shell/shell.qml
That is line 757 on omarchy 4.0.2-1 and line 1470 in v4.0.3, which shipped on 2026-09-08 and rewrote much of that file without touching this line.
Two pull requests offer fixes and neither has landed as of 2026-09-11: #9606 (restart the shell when the cache cannot be cleared, closed unmerged on 2026-09-06) and #8766 (Quickshell.reload(false), still open and gated on quickshell-mirror/quickshell#956, a use-after-free at engine generation teardown that is also still open).
One case is stale by design rather than by this bug. From 4.0.3, shell/README.md states that a service marked keepLoaded stays mounted across a plugin hot reload so that tearing down a changed widget cannot destroy omarchy.lock while the session is locked. That instance is never replaced, so edits to a keepLoaded service take effect only on a shell restart even if the component cache is fixed.
Fix
Restart the shell after any plugin change. A fresh process compiles the plugin from source:
omarchy restart shell # same as: omarchy-restart-shell
Do not use omarchy refresh shell for this. That command runs omarchy-refresh-config omarchy/shell.json and omarchy-bar defaults before restarting, so it resets your shell configuration. omarchy-restart-shell refuses to run while the session is locked, so unlock first.
Verify
Add a marker to the plugin before restarting and look for it afterwards:
Component.onCompleted: console.warn("plugin reloaded")
omarchy restart shell
journalctl --user -b -t omarchy-shell -n 50 --no-pager | grep 'plugin reloaded'
Three reporters confirmed the marker fires only after the restart, never after the automatic reload.
Sources
- https://github.com/omacom/omarchy/issues/6981
- https://github.com/omacom/omarchy/blob/quattro/shell/shell.qml
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-restart-shell
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-refresh-shell
- https://github.com/omacom/omarchy/pull/9606
- https://github.com/omacom/omarchy/pull/8766
- https://github.com/omacom/omarchy/issues/9772
- https://github.com/omacom/omarchy/blob/v4.0.3/shell/shell.qml
- https://github.com/omacom/omarchy/blob/v4.0.2/shell/shell.qml
- https://github.com/omacom/omarchy/blob/v4.0.0-beta3/shell/shell.qml
- https://github.com/omacom/omarchy/blob/v4.0.3/shell/README.md
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-plugin-update
- https://github.com/omacom/omarchy/compare/v4.0.2...v4.0.3
- https://github.com/quickshell-mirror/quickshell/issues/956