NousResearch/hermes-agent

llama.cpp alias fallback routing fixes

Cluster 119227. Data as of

Nothing open on GitHub. Fix merged in #131795 on 2 Oct 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 #131795. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #131795. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address incorrect routing behavior when falling back to llama.cpp aliases, including a bug where the alias was sent to an unrelated cloud provider and a fix to resolve aliases to the correct local managed endpoint. A related item salvages a previous attempt to make Desktop-managed llama.cpp fallback work rather than error.

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.

  • #131795 Fallback to a Desktop-managed llama.cpp model works instead of failing "provider not configured" (#119227, salvage #119228)

    merged to main

    files: agent/auxiliary_client.py, agent/auxiliary_local_runtime.py, agent/auxiliary_unavailable.py, contributors/emails/[email protected], tests/agent/test_llamacpp_alias_managed_endpoint.py, website/docs/user-guide/features/fallback-providers.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #119228 fix(fallback): resolve llama.cpp aliases to the managed local endpoint · merged via another change → 0989767, #131795
Closed issues · 1
  • Closed#119227Fallback to a llamacpp alias posts the local model slug to an unrelated cloud provider, then reports it as a context-size rejection
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

Merged PRs
#131795
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
2 Oct 2026

For your agent

The same facts, typed.