NousResearch/hermes-agent

Linux desktop entry Exec path flip fixes

Cluster 112795. Data as of 2026-10-24 11:53 UTC

Nothing open on GitHub. Fix merged in #113091 on 16 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #113091. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #113091. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #113091, then check it covers your case.

Read #113091 Pick up a Lab task

Multiple attempts to fix a recurring bug where the Linux desktop launcher's Exec field alternates between venv and wrapper paths across update cycles. The fixes address deferred writes, PATH resolution, and checkout ownership gating for the desktop entry resolver.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

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

#113091 fix(linux): desktop launcher Exec no longer flips between venv and wrapper across updates (#112795, salvage #112798)

merged to main

files: hermes_cli/linux_desktop_entry.py, tests/hermes_cli/test_linux_desktop_entry.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

#112798 fix(linux): a PATH hit inside the checkout never persists as desktop entry Exec · merged via another change → b5f3ed7
#112802 fix(desktop): gate the rerouted desktop-entry resolver hit on checkout ownership · superseded by another PR → #112798

Closed issues · 1

Closed#112795Linux: hermes.desktop still alternates Exec forms across an update cycle — third fix needed; the deferred write from #111906 still lands inside gnome-shell STARTING

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.50: 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

Merged PRs: #113091
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/112795.json
cluster/112795.md