NousResearch/hermes-agent

GPU vendor detection and build selection fixes

Cluster 100740 · hermes cli. Data as of

1 open item. Fix merged in #131782 on 3 Oct 2026. Check it covers your case.

The short answer

0open issues
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #131782. 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
0 issues and 1 PR.

These members address incorrect GPU build selection in the local runtime, where AMD and Intel GPUs were not being matched to appropriate Vulkan or SYCL builds due to a vendor probe that only recognized NVIDIA hardware. Changes add proper vendor detection and a vulkaninfo fallback.

Open issues0

No open issues.

Open PRs1

  • PR#102505feat(local-runtime): use SYCL builds on Intel GPUs + add vulkaninfo detection fallback

Fixes on record

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

  • #131782 fix(local-runtime): AMD/Intel GPUs get the Vulkan build and are sized by their own memory (salvage #129750, #109336, #115076)

    merged to main

    files: contributors/emails/[redacted:email], hermes_cli/local_runtime/bootstrap.py, hermes_cli/local_runtime/devices.py, hermes_cli/local_runtime/endpoint.py, hermes_cli/local_runtime/hardware.py, hermes_cli/web_routers/local_models.py, tests/hermes_cli/test_local_launch_budget.py, tests/hermes_cli/test_local_quickstart.py, tests/hermes_cli/test_local_runtime.py, tests/hermes_cli/test_unified_pool_quirk.py, website/docs/user-guide/local-models.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #100749 fix(local-runtime): use Vulkan builds on AMD and Intel GPUs · merged via another change → 8abd6dc, c8301ea, #129750, #131782
Closed issues · 1
  • Closed#100740Managed local runtime installs CPU llama.cpp build on AMD/Intel GPU machines — vendor probe is NVIDIA-only, Vulkan never selected
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

Subsystem
hermes cli
Merged PRs
#131782
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
3 Oct 2026

For your agent

The same facts, typed.