Cairn
NousResearch/hermes-agent

llamacpp endpoint resolution ignores user config

Cluster 116143. Data as of

Nothing open on GitHub. Fix merged in #116679 on 20 Sep 2026. Check it covers your case.

The short answer

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

These items address a bug where the llamacpp provider's endpoint resolution ignores user-configured ports and provider entries, instead defaulting to its own detection logic. The changes aim to make configured llamacpp endpoints and ports take precedence correctly.

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.

  • #116679 fix(local-models): a user-run llama.cpp server on a configured port resolves from /model and providers.llamacpp (#116249, #116143, salvage #116156, #116292)

    merged to main

    files: contributors/emails/hermes@local, hermes_cli/inventory.py, hermes_cli/model_switch.py, hermes_cli/providers.py, hermes_cli/runtime_provider_custom.py, tests/hermes_cli/test_local_runtime.py, website/docs/user-guide/local-models.md

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #116156 fix(provider): let configured llamacpp endpoints serve new sessions · merged via another change → 581af46, #116679, #116249, #116143, #116156, #116292
  • #116167 fix(runtime): prefer configured llamacpp provider entries · done elsewhere → 581af46, #116679, #116249, #116143, #116156, #116292
Closed issues · 1
  • Closed#116143llamacpp alias hijacks user-configured provider: resolve_llamacpp_endpoint() ignores local_runtime.detect_ports and providers entry
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

Merged PRs
#116679
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
20 Sep 2026

For your agent

The same facts, typed.

cluster/116143.json
cluster/116143.md