# NousResearch/hermes-agent · Named custom providers not recognized as aggregators

## Open now

- Nothing open on GitHub.

These issues and pull requests address a bug where custom:<name> providers were not being treated as aggregators, particularly when handling vendor-prefixed slugs. Fixes span the CLI, doctor, and providers layers.

## 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

- #26578: custom:<name> providers not recognized as aggregators (custom:zenmux)

## Prior & competing PRs

- **#26591: fix(cli): treat named custom providers as aggregators**. closed without merge · fix tier `suggested`
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#26594`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#26594: fix(providers): treat custom:<name> as aggregator for vendor-prefixed slugs (#26578)**. closed without merge
  - maintainer direction: category `volume_quota`; implication `active`

## Fix status

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