# NousResearch/hermes-agent · Memory provider initialization and session stability fixes

## Open now

- Nothing open on GitHub.

These members address bugs where memory-related components reinitialize or respawn unnecessarily on repeated calls or turns. Themes include guarding against duplicate initialization and preventing per-session process or agent churn.

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

- #20939: \[Bug\]: MemOS memory provider spawns new bridge.cts process on every turn instead of once per session

## Prior & competing PRs

- **#20961: fix: guard memory provider initialize() against repeated calls (#20939)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `d6c53dcdcb49694b382000b53f194b99d97aa72d`
- **#21299: fix(gateway): prevent per-turn agent eviction from model normalization mismatch and signature instability**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

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