NousResearch/hermes-agent

Linux desktop launcher management and venv path issues

Cluster 101097. Data as of 2026-10-25 11:21 UTC

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

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #104852. 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: Nothing open on GitHub.

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

Read #104852 Pick up a Lab task

These items concern problems with how Linux .desktop launcher entries are generated and rewritten on each launch, including a venv symlink resolution issue causing missing modules and options to preserve or opt out of automatic launcher management.

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.

#104852 fix(desktop): preserve customized Linux launchers when management is disabled

merged to main

files: contributors/emails/[email protected], evals/desktop_bug_campaign/linux_launcher_probe.py, evals/desktop_bug_campaign/native_ready_probe.mjs, hermes_cli/config_defaults.py, hermes_cli/linux_desktop_entry.py, tests/hermes_cli/test_linux_launcher_management.py, website/docs/user-guide/desktop.md

1 PR closed without merging

From the close comments: superseded by another PR 1

#101453 fix(desktop): add manage_launcher_entry opt-out so hermes.desktop edits survive every launch · superseded by another PR → 7252d40, #104852

Closed issues · 1

Closed#101097hermes desktop: generated .desktop Exec resolves venv symlink to base interpreter (silent ModuleNotFoundError: yaml), and rewrites entry every launch

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.67: 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: #104852
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 7 Sep 2026

For your agent

The same facts, typed.

cluster/101097.json
cluster/101097.md