# NousResearch/hermes-agent · Silent memory loss on provider migration at startup

## Open now

- Nothing open on GitHub.

These items address a scenario where a memory provider migration at agent startup only logs to agent.log, causing silent data loss when allow_lazy_installs is false. The proposed fixes aim to surface migration outcomes through a warning sink so users are notified.

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

- #119769: Memory-provider migration outcome at agent start is agent.log-only; with allow_lazy_installs: false the user loses memory silently

## Prior & competing PRs

- **#131269: fix(memory): never lose memory silently when a provider moves out of core**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/agent_init.py`, `agent/status_output.py`, `agent/turn_context.py`, `hermes_cli/memory_provider_migration.py`, `hermes_cli/plugins_cmd_install.py`, `hermes_cli/plugins_transaction.py`, `tests/agent/test_memory_migration_notifications.py`, `tests/hermes_cli/test_memory_provider_migration.py`, `website/docs/user-guide/features/memory-providers.md`
- **#119775: fix(memory): surface startup migration outcomes through warning sink**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `0cdba5ec7e`, `#131269`

## Fix status

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