# NousResearch/hermes-agent · Auth registry control for replacement provider plugins

## Open now

- Nothing open on GitHub.

These items address how replacement provider plugins interact with the auth registry, specifically around aliases, display names, and ownership of ProviderProfile versus PROVIDER_REGISTRY responsibilities.

## 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 #117655. Verify it addresses your case.
- **Recommended:** read PR #117655 (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-117655`. 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

- #116668: fix(provider-auth): replacement plugins can split ProviderProfile and PROVIDER_REGISTRY ownership

## Prior & competing PRs

- **#117655: fix(auth): a user provider plugin's aliases and display name win in the auth registry (#116668)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/auth_plugin_providers.py`, `tests/providers/test_auth_registry_mid_discovery.py`
- **#116695: fix(provider-auth): keep replacement plugins in control of auth**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `5aeddb6c8591`, `#117655`

## Fix status

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