Cairn
NousResearch/hermes-agent

Linux .desktop launcher interpreter resolution fixes

Cluster 92086 · apps/desktop. Data as of

2 open items. Fix merged in #99492 on 31 Aug 2026. Check it covers your case.

The short answer

0open issues
2open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #99492. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 2 PRs.

These issues and PRs address a problem where the Linux .desktop Exec= entry points to an interpreter lacking the hermes_cli module, particularly in uv-managed or symlinked Python environments. The work focuses on resolving a Hermes-capable interpreter path for the launcher.

Open issues0

No open issues.

Open PRs2

  • PR#92090fix(desktop-entry): keep the venv interpreter in Exec= instead of its symlink target
  • PR#92122fix(desktop): resolve a Hermes-capable interpreter for the .desktop Exec

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #99492 fix(cli): launch-context-independent Linux desktop-entry Exec (salvage #94874 + #87937)

    merged to main

    files: apps/desktop/scripts/run-electron-builder.mjs, contributors/emails/[redacted:email], contributors/emails/[redacted:email], hermes_cli/gui_uninstall.py, hermes_cli/linux_desktop_entry.py, tests/hermes_cli/test_linux_desktop_entry.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #92088 fix(desktop): resolve a Hermes-capable interpreter for the .desktop Exec · superseded by another PR → #92122
  • #94874 fix(cli): persist a launch-context independent desktop-entry Exec · done elsewhere → #99492
Closed issues · 1
  • Closed#92086Linux .desktop launcher fails silently when sys.executable lacks hermes_cli (e.g. uv-managed install)
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
apps/desktop
Merged PRs
#99492
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
31 Aug 2026

For your agent

The same facts, typed.

cluster/92086.json
cluster/92086.md