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-install-hermes-cli installs via pipx/PyPI, which Hermes' own docs list as unsupported
Reported by vaibhavb · filed Sep 15, 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
Description
omarchy-install-hermes-cli installs Hermes Agent viamise use -g pipx:hermes-agent[extras=all] (pip/PyPI under the hood).
Hermes' own Platform Support docs explicitly list pip/PyPI installs
(pip install hermes-agent, uv tool install hermes-agent) as
Unsupported: "PRs to fix them will not be accepted, and any code
that keeps compatibility with them may be removed at any point."
https://hermes-agent.nousresearch.com/docs/getting-started/platform-support
The officially supported distribution method on Linux iscurl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash,
which git-clones the full repo rather than installing a wheel.
Concrete breakage observed
The pip wheel for hermes-agent 0.19.0 (v2026.7.20) does not includescripts/whatsapp-bridge/ at all (confirmed via the wheel's RECORD file),
so hermes whatsapp fails immediately with "Bridge script not found."
This is a direct consequence of pip/PyPI being an unsupported/best-effort
distribution method upstream — filed as
NousResearch/hermes-agent#111698 for visibility, but upstream is unlikely
to prioritize a fix given their stated support policy.
Why omarchy-install-hermes-cli uses pipx anyway
The script's own comments explain this is deliberate — Hermes pins
Requires-Python >=3.11,<3.14 and mise's pipx backend is used to build an
isolated interpreter, which the git-clone installer doesn't need to solve
the same way.
Suggested fix
Either:
1. Switch omarchy-install-hermes-cli to the officially supported
install.sh git-clone method (may need a wrapper to keep the
Python-version pinning it currently gets from mise/pipx), or
2. If pipx must be kept, detect and vendor/fetch missing runtime assets
(like scripts/whatsapp-bridge/) that pip's wheel omits, so
Omarchy-installed Hermes doesn't silently break on features that work
fine via the supported installer.
Environment
- omarchy 4.0.3-1
- hermes-agent 0.19.0 (v2026.7.20) via pipx
View raw text
### Description `omarchy-install-hermes-cli` installs Hermes Agent via `mise use -g pipx:hermes-agent[extras=all]` (pip/PyPI under the hood). Hermes' own Platform Support docs explicitly list pip/PyPI installs (`pip install hermes-agent`, `uv tool install hermes-agent`) as **Unsupported**: "PRs to fix them will not be accepted, and any code that keeps compatibility with them may be removed at any point." https://hermes-agent.nousresearch.com/docs/getting-started/platform-support The officially supported distribution method on Linux is `curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash`, which git-clones the full repo rather than installing a wheel. ### Concrete breakage observed The pip wheel for hermes-agent 0.19.0 (v2026.7.20) does not include `scripts/whatsapp-bridge/` at all (confirmed via the wheel's RECORD file), so `hermes whatsapp` fails immediately with "Bridge script not found." This is a direct consequence of pip/PyPI being an unsupported/best-effort distribution method upstream — filed as NousResearch/hermes-agent#111698 for visibility, but upstream is unlikely to prioritize a fix given their stated support policy. ### Why omarchy-install-hermes-cli uses pipx anyway The script's own comments explain this is deliberate — Hermes pins Requires-Python >=3.11,<3.14 and mise's pipx backend is used to build an isolated interpreter, which the git-clone installer doesn't need to solve the same way. ### Suggested fix Either: 1. Switch `omarchy-install-hermes-cli` to the officially supported `install.sh` git-clone method (may need a wrapper to keep the Python-version pinning it currently gets from mise/pipx), or 2. If pipx must be kept, detect and vendor/fetch missing runtime assets (like scripts/whatsapp-bridge/) that pip's wheel omits, so Omarchy-installed Hermes doesn't silently break on features that work fine via the supported installer. ### Environment - omarchy 4.0.3-1 - hermes-agent 0.19.0 (v2026.7.20) via pipx
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
- Fixed bypr/12836· confirmed
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 13:40 UTC