# NousResearch/hermes-agent · llamacpp port detection config not forwarded

## Open now

- Nothing open on GitHub.

These issues and PRs concern a bug where the llamacpp provider fails to detect a running llama-server on non-default ports because the configured detection ports are not properly passed through to the endpoint resolution logic.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #105834: llamacpp provider not detected when llama-server runs on a non-default port (detect_ports ignored in _llamacpp_pdef)

## Prior & competing PRs

- **#105837: fix(providers): forward config to resolve_llamacpp_endpoint for detect_ports (#105834)**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `2cfb655d5`, `95464a7b2`
- **#105847: fix(llamacpp): honor configured detection ports**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#105837`, `#105834`

## Fix status

- No merged fix on record.