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.
omarchy plugin add --enable aborts with "omarchy-shell is not responding" when many plugins are installed
Reported by Nejcc · filed Oct 7, 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 happens
$ omarchy plugin add https://github.com/<owner>/<plugin>.git --enable
...
Added <id> into ~/.config/omarchy/plugins/<id>
omarchy-shell is not respondingThe plugin is cloned but never enabled. Running omarchy plugin enable <id> a few seconds later works.
Why
In bin/omarchy-plugin-add, mv "$stage" "$target" lands the plugin under ~/.config/omarchy/plugins/, and the shell's watcher reloads all plugin code. The next line, omarchy-shell shell rescanPlugins, uses the default 2s IPC timeout in bin/omarchy-shell (OMARCHY_SHELL_IPC_TIMEOUT). With around 18 third-party plugins installed the reload takes longer than that, so the call times out, fail exits, and the enable step never runs. The same thing happens to any omarchy-shell call made right after a file change under the plugins directory.
Suggested fix
Before rescanPlugins (and before omarchy-plugin-enable), wait for the shell to answer: retry omarchy-shell shell ping for a bounded time (e.g. 30s), or call these with a longer OMARCHY_SHELL_IPC_TIMEOUT. A rescan that fails after the move could also print the omarchy plugin enable <id> hint instead of a bare error.
Seen on Omarchy 4.0.4, Hyprland 0.56.2.
View raw text
## What happens ``` $ omarchy plugin add https://github.com/<owner>/<plugin>.git --enable ... Added <id> into ~/.config/omarchy/plugins/<id> omarchy-shell is not responding ``` The plugin is cloned but never enabled. Running `omarchy plugin enable <id>` a few seconds later works. ## Why In `bin/omarchy-plugin-add`, `mv "$stage" "$target"` lands the plugin under `~/.config/omarchy/plugins/`, and the shell's watcher reloads all plugin code. The next line, `omarchy-shell shell rescanPlugins`, uses the default 2s IPC timeout in `bin/omarchy-shell` (`OMARCHY_SHELL_IPC_TIMEOUT`). With around 18 third-party plugins installed the reload takes longer than that, so the call times out, `fail` exits, and the enable step never runs. The same thing happens to any `omarchy-shell` call made right after a file change under the plugins directory. ## Suggested fix Before `rescanPlugins` (and before `omarchy-plugin-enable`), wait for the shell to answer: retry `omarchy-shell shell ping` for a bounded time (e.g. 30s), or call these with a longer `OMARCHY_SHELL_IPC_TIMEOUT`. A rescan that fails after the move could also print the `omarchy plugin enable <id>` hint instead of a bare error. Seen on Omarchy 4.0.4, Hyprland 0.56.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 22:14 UTC