NousResearch/hermes-agent

NVIDIA vendor slug recognition in doctor checks

Cluster 35425 · hermes cli. Data as of

Nothing open on GitHub. Fix merged in #46822 on 15 Jun 2026. Check it covers your case.

The short answer

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

These items relate to fixing the doctor command to correctly recognize and accept NVIDIA as a valid vendor slug provider. The work addresses a bug in vendor slug configuration handling.

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.

  • #46822 fix(doctor): accept NVIDIA vendor slugs

    merged to main

    files: hermes_cli/doctor.py, tests/hermes_cli/test_doctor.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #35438 fix(doctor): recognize nvidia as vendor-slug-accepting provider · merged via another change → #46822
Closed issues · 1
  • Closed#35425bug, configuration
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
hermes cli
Merged PRs
#46822
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
15 Jun 2026

For your agent

The same facts, typed.