# NousResearch/hermes-agent · Built-in aggregator row loses models on duplicate upstream

## Open now

- Nothing open on GitHub.

A bug where a built-in aggregator row has its models incorrectly stripped when a user-defined providers entry references the same upstream. Multiple fixes and reports address this overlap-stripping behavior in build_models_payload.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #116733. Verify it addresses your case.
- **Recommended:** read PR #116733 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-116733`. 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

- #115623: \[Bug\]: build_models_payload empties a built-in provider row when a providers: entry duplicates the same upstream (aggregator overlap strip)

## Prior & competing PRs

- **#116733: fix(model-picker): a built-in aggregator row keeps its models when a providers: entry duplicates the same upstream (#115623, salvage #115627)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/inventory.py`, `tests/hermes_cli/test_aggregator_overlap_twin_upstream.py`
- **#115627: fix(model-picker): built-in aggregator row keeps its models when a user row duplicates the same upstream**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `2d1ccf447252`, `#116733`, `#115623`, `#115627`

## Fix status

- Merged to main in PR #116733 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-20`.
