# NousResearch/hermes-agent · Named provider presets and multi-endpoint config support

## Open now

- Nothing open on GitHub.

These items propose support for defining multiple named provider configurations or presets in YAML, with the ability to select or switch between them via CLI or a selectable list. The themes are closely related around flexible, multi-endpoint provider configuration.

## TL;DR

- 3 member(s): 0 open issue(s), 2 closed issue(s), 0 open PR(s), 0 merged PR(s), 1 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_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.45`: 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

- #1891: Feature Request: Multiple Provider Presets in YAML Config
- #47039: \[Feature Request\]: Support multiple API endpoints per provider with selectable list in \`custom\` provider

## Prior & competing PRs

- **#2097: feat(provider): named provider presets with /provider switching and hermes provider CLI**. closed without merge · fix tier `suggested`
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._

## Fix status

- No merged fix on record.
- Subsystem: `agent`