# NousResearch/hermes-agent · Profile config changes lost or misread during rescans

## Open now

- Nothing open on GitHub.

These issues and fixes concern secondary profile configuration saved during an adapter connection being incorrectly handled by subsequent rescans. The work addresses preserving profile config changes so they are neither missed nor incorrectly picked up at the wrong time.

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

- #109398: Secondary profile config saved during adapter connection is missed by later rescans

## Prior & competing PRs

- **#110203: Secondary profile config saved during an adapter connection is picked up by the next rescan (#109398, salvage #109399)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/run_adapters.py`, `gateway/run_profile_reconcile.py`, `tests/gateway/test_profile_signature_during_connect.py`
- **#109399: fix(gateway): preserve profile config changes during connection**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `a15b8982d474`, `#110203`

## Fix status

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