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.
hermes-desktop launcher always skips the existing install (HERMES_DESKTOP_IGNORE_EXISTING=1 hardcoded)
Reported by spideranged · filed Sep 27, 2026Closed upstream on 2026-09-29 by the merge of PR omacom/omarchy-pkgs#718 (closed by spencerbull). GitHub close reason: completed.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
\/usr/bin/hermes-desktop\ (from the \hermes-desktop\ package, currently 2026.8.31-3)
unconditionally sets:
export HERMES_DESKTOP_IGNORE_EXISTING=1
before launching the app. Per the app's own source
(apps/desktop/electron/main.ts, around the ACTIVE_HERMES_ROOT resolution):
"If the active runtime is usable, launch it directly; only fall through to
bootstrap when the runtime itself is unusable. HERMES_DESKTOP_IGNORE_EXISTING=1
skips this rung."
Because the launcher always sets this variable, Hermes Desktop never takes the
"launch the existing, working install directly" path — every launch is forced
through the first-run/bootstrap flow instead, regardless of whether
~/.hermes/hermes-agent is already installed and healthy.
Reproduced directly: right after a bootstrap run completed successfully and
wrote a valid, current \.hermes-bootstrap-complete\ marker, launching
hermes-desktop again still dropped into first-run setup rather than using
that install. ~/.hermes/logs/desktop.log shows:
[bootstrap] HERMES_DESKTOP_IGNORE_EXISTING=1; skipping the installed runtime
at /home/q/.hermes/hermes-agent
[boot] Waiting for first-run setup choice
This matches a real-world symptom of the app repeatedly bouncing back to a
first-run "install" screen on relaunch, even after a working install had just
been confirmed.
Expected: on a normal launch, with a usable existing runtime present,
Hermes Desktop should launch it directly rather than forcing first-run setup.
Workaround: removing the \export HERMES_DESKTOP_IGNORE_EXISTING=1\ line
from \/usr/bin/hermes-desktop\ restores the "launch directly if usable"
behavior.
System: Omarchy, hermes-desktop 2026.8.31-3.
Filed by Claude (Sonnet 5) via Claude Code.
View raw text
\`/usr/bin/hermes-desktop\` (from the \`hermes-desktop\` package, currently 2026.8.31-3)
unconditionally sets:
export HERMES_DESKTOP_IGNORE_EXISTING=1
before launching the app. Per the app's own source
(apps/desktop/electron/main.ts, around the ACTIVE_HERMES_ROOT resolution):
"If the active runtime is usable, launch it directly; only fall through to
bootstrap when the runtime itself is unusable. HERMES_DESKTOP_IGNORE_EXISTING=1
skips this rung."
Because the launcher always sets this variable, Hermes Desktop never takes the
"launch the existing, working install directly" path — every launch is forced
through the first-run/bootstrap flow instead, regardless of whether
~/.hermes/hermes-agent is already installed and healthy.
Reproduced directly: right after a bootstrap run completed successfully and
wrote a valid, current \`.hermes-bootstrap-complete\` marker, launching
hermes-desktop again still dropped into first-run setup rather than using
that install. ~/.hermes/logs/desktop.log shows:
[bootstrap] HERMES_DESKTOP_IGNORE_EXISTING=1; skipping the installed runtime
at /home/q/.hermes/hermes-agent
[boot] Waiting for first-run setup choice
This matches a real-world symptom of the app repeatedly bouncing back to a
first-run "install" screen on relaunch, even after a working install had just
been confirmed.
**Expected:** on a normal launch, with a usable existing runtime present,
Hermes Desktop should launch it directly rather than forcing first-run setup.
**Workaround:** removing the \`export HERMES_DESKTOP_IGNORE_EXISTING=1\` line
from \`/usr/bin/hermes-desktop\` restores the "launch directly if usable"
behavior.
System: Omarchy, hermes-desktop 2026.8.31-3.
Filed by Claude (Sonnet 5) via Claude Code.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.
No decision has been recorded yet.