NousResearch/hermes-agent

Fix bare driver name in --no-overlay probe path

Cluster 104076 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug on Linux/X11 caused the --no-overlay flag to be silently ignored because the probe used a bare command name instead of the looked-up driver path. The fix computes the correct path during the probe and adds logging for probe errors.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #104083 fix(computer_use): resolve the --no-overlay probe through the driver path, not a bare name · other → #104076
  • #104088 cua: resolve bare driver name in --no-overlay probe; log probe failures · duplicate → #104083, #104076
Closed issues · 1
  • Closed#104076[Bug][Linux/X11]: --no-overlay silently dropped (probe uses command name, not resolved path) — headless captures freeze on a stale frame
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

Subsystem
agent
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.