computer-use doctor detecting broken cua-driver daemons
NousResearch/hermes-agent · cluster 114748
Data as of
Nothing open on GitHub. Fix merged in #116823. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #116823. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117047. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address cases where computer-use doctor and status commands fail to detect or report dead or misconfigured cua-driver daemon units, particularly when the daemon's executable path points to a pruned release. The work focuses on surfacing these broken states rather than silently reporting ok.
Open issues0
Open PRs0
Fixes on record
-
#116823 fix(computer-use): doctor names a daemon unit whose cua-driver Exec target was pruned (#114748, salvage #114907)
files:
tests/tools/test_computer_use_doctor_stale_units.py,tools/computer_use/doctor.py -
#117047 fix(computer-use): doctor and status report a configured cua-driver daemon whose serve is not listening (#114748, supersedes #114928)
files:
hermes_cli/subcommands/computer_use.py,tests/tools/test_computer_use_doctor_stale_units.py,tools/computer_use/cua_backend.py,tools/computer_use/doctor.py,website/docs/user-guide/features/computer-use.md
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
-
#114907 fix(computer_use): surface daemon units pointing at pruned cua-driver releases in doctor · merged via another change →
a731e7e,#116823,#114748,#114907 -
#114928 fix(computer-use): doctor detects a dead serve daemon (and a pruned unit path) instead of reporting ok · done elsewhere →
f9d6d04,#117047,#114748,#114928
Closed issues · 1
- Closed#114748[Bug]: dead cua-driver daemon (ExecStart points at a pruned release) is invisible to computer_use auto-repair and `computer-use doctor`
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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