Cairn
NousResearch/hermes-agent

Linux NVIDIA backend falls back to Vulkan, not CUDA

Cluster 103949. 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.

These items address a situation where Linux with NVIDIA hardware selects CUDA but no prebuilt CUDA assets exist, causing automatic backend selection to fail. The fix redirects Linux NVIDIA to use Vulkan instead.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #102571 fix(cli): local-model setup falls back to vulkan when Linux CUDA has no prebuilt · superseded by another PR → bdb52ce
  • #104755 fix(local-runtime): select vulkan for NVIDIA on Linux due to absence of prebuilt CUDA assets (#103949) · superseded by another PR → bdb52ce
Closed issues · 1
  • Closed#103949local_runtime: select_backend() returns 'cuda' on Linux+NVIDIA but no Linux CUDA prebuilt exists — auto backend fails unconditionally
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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/103949.json
cluster/103949.md